Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a0abb1a59da0afc5c0153f2307364585b51d7b8a494dbb3919d6e59bfc6501f

Tx prefix hash: cecfe5c2aef7474ab166d0c2b7df1a42bd6a75f19596372c15694800aa8b8858
Tx public key: f1de58346c8c8c18b5ab82ca0d352dc62b73fe2c6ed02fd1eab1f055718f0fb5
Timestamp: 1772015572 Timestamp [UTC]: 2026-02-25 10:32:52 Age [y:d:h:m:s]: 00:267:18:10:03
Block: 1485463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196940 RingCT/type: yes/0
Extra: 01f1de58346c8c8c18b5ab82ca0d352dc62b73fe2c6ed02fd1eab1f055718f0fb5021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ee7cc0ed42fcf29da9072fe8e081398213f1fee0cde5a527fe378b4bc668f85 0.000600000000 1974899 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": 1485473, "vin": [ { "gen": { "height": 1485463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ee7cc0ed42fcf29da9072fe8e081398213f1fee0cde5a527fe378b4bc668f85" } } ], "extra": [ 1, 241, 222, 88, 52, 108, 140, 140, 24, 181, 171, 130, 202, 13, 53, 45, 198, 43, 115, 254, 44, 110, 208, 47, 209, 234, 177, 240, 85, 113, 143, 15, 181, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: