Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fbb3c0319f9183d8d5d1dd3e73d808667825857e5e202f7f1b9a1feb38e70a22

Tx prefix hash: 31ad273217950a48611a56bf0f7519f41771fbf5b441bf574c274931d73ef3af
Tx public key: 38cc2d464c97afed69e25a24cc84b69fb2e73a461144fce8c4d7c9cc55becca6
Timestamp: 1756340013 Timestamp [UTC]: 2025-08-28 00:13:33 Age [y:d:h:m:s]: 00:263:07:26:34
Block: 1355914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180592 RingCT/type: yes/0
Extra: 0138cc2d464c97afed69e25a24cc84b69fb2e73a461144fce8c4d7c9cc55becca60211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eafef96a38995598bb1bb18bdbb3fa694d8c5e48374b2c81640391aeed34cfc9 0.000600000000 1843917 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1355924, "vin": [ { "gen": { "height": 1355914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eafef96a38995598bb1bb18bdbb3fa694d8c5e48374b2c81640391aeed34cfc9" } } ], "extra": [ 1, 56, 204, 45, 70, 76, 151, 175, 237, 105, 226, 90, 36, 204, 132, 182, 159, 178, 231, 58, 70, 17, 68, 252, 232, 196, 215, 201, 204, 85, 190, 204, 166, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: