Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a81672f96af45cfc4cc1cdf162c34210569fad8ee7ab4a2baaee6ada5b3482bb

Tx prefix hash: 718ed023f8c1aadc6107bf122ab6094462097f2ffc1c30e5fb52b21c47e7fe28
Tx public key: ee7c9f258a4d201b98d6613e22d0974507cdddef451b04d3c0febc46f3dc0025
Timestamp: 1747574061 Timestamp [UCT]: 2025-05-18 13:14:21 Age [y:d:h:m:s]: 00:255:21:30:51
Block: 1285617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180514 RingCT/type: yes/0
Extra: 01ee7c9f258a4d201b98d6613e22d0974507cdddef451b04d3c0febc46f3dc00250211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136a450cceb9f1b854c9882efdd9dc77aa7d64db5ab181491655821733d2acf6 0.600000000000 1773082 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 dinasty-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": 1285627, "vin": [ { "gen": { "height": 1285617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136a450cceb9f1b854c9882efdd9dc77aa7d64db5ab181491655821733d2acf6" } } ], "extra": [ 1, 238, 124, 159, 37, 138, 77, 32, 27, 152, 214, 97, 62, 34, 208, 151, 69, 7, 205, 221, 239, 69, 27, 4, 211, 192, 254, 188, 70, 243, 220, 0, 37, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8