Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9651936bf865a6733447f2fef85908a9fe47298e480aebbe3407cb451a8467a

Tx prefix hash: 17675bb14ada41d6dba49cdf75aeff74d728fad4069d324186c8a0230a82d8b8
Tx public key: 6e507e3dfa53ff6e68c166b1ce5b947bec9a894c38276c6a245b843c3d0173ef
Timestamp: 1742900284 Timestamp [UCT]: 2025-03-25 10:58:04 Age [y:d:h:m:s]: 00:246:03:26:13
Block: 1246928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173663 RingCT/type: yes/0
Extra: 016e507e3dfa53ff6e68c166b1ce5b947bec9a894c38276c6a245b843c3d0173ef02110000000624ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2bd8fedf9c362ac03905a9c3d376e8854f64f9778e08be123fa5978149c4e91 0.600000000000 1733929 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": 1246938, "vin": [ { "gen": { "height": 1246928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2bd8fedf9c362ac03905a9c3d376e8854f64f9778e08be123fa5978149c4e91" } } ], "extra": [ 1, 110, 80, 126, 61, 250, 83, 255, 110, 104, 193, 102, 177, 206, 91, 148, 123, 236, 154, 137, 76, 56, 39, 108, 106, 36, 91, 132, 60, 61, 1, 115, 239, 2, 17, 0, 0, 0, 6, 36, 255, 78, 161, 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