Transaction
F5179E7182392E…5C913F168D37
Block 447,368 · index 1 · indexed
Summary
- Hash
- F5179E7182392E9FB4B4EC5F4F6AD380C218BB56185E30C714BE5C913F168D37
- Block
- 447,368
- Size
- 1974 bytes
- Gas used
- 9,352,510 / 13,555,164
- Fee
- 14911ugnot
- Status
- success
Messages
- Attached funds
- —
- Package
- gno.land/r/moul/home
- Function
- Set
Arguments · 2
- #1layout
- #2<gno-columns>  <gno-columns-sep /> # Manfred Touron :bio: :social: </gno-columns> ## Now :now: ## Packages :packages: :about: --- :reactions: --- [:realm:](/r/moul/home:slots) · rev :rev: · :chainid: @ :height: On mygnoscan: :scan.links:
- Attached funds
- —
- Package
- gno.land/r/moul/home
- Function
- Set
Arguments · 2
- #1now
- #2- **One package a day**, under `x/daily`: small and finished, each one a question about what Gno can express, answered. The current count is in Packages below, because a number typed here would be wrong by next week. - **[mygnoscan](https://github.com/gnoverse/mygnoscan)**, an explorer for gno chains. It is the only one that distinguishes a package that is live from one that was uploaded and is still waiting to be approved. - **[A blog that is a realm](/r/moul/blog).** Every post is an entry in an on-chain store, published by a transaction. Same trick as this page. - **[A gallery of ascii and pixel art](/r/moul/gallery/v0).** It stores nothing: every piece lives in the realm its author put it in, and the gallery renders the ones it can import. - **Mainnet.** gno.land is launched. The interesting part is no longer the chain, it is what is running on it. - **[Bubble Rumble](https://bubblerumble.net/?ref=g1manfred47kzduec920z88wfr64ylksmdcedlf5).** Jae Kwon's last-boop-wins pot game, real GNOT on mainnet, with a whole multiplayer client grown around it in a week. That link is my invite: boop through it and we both earn its BUBBLE token.
- Attached funds
- —
- Package
- gno.land/r/moul/home
- Function
- Delete
Arguments · 1
- #1gallery
Result log
msg:0,success:true,log:,events:[] msg:1,success:true,log:,events:[] msg:2,success:true,log:,events:[]