Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 037fd88bcdfd60f60f78121f7d7a7d4c041bcc83c9826b162b2359dec4725bf5

Tx prefix hash: 44700678f6a53cf2dea99cdbcbb0df7ad5374106aa304b899154ae1cbaf7afd1
Tx public key: 58a3c8d1bdcb099cb83da49e1bdd6a8dcffae5ab446611c314dc281627eae9b6
Timestamp: 1712041204 Timestamp [UCT]: 2024-04-02 07:00:04 Age [y:d:h:m:s]: 00:290:15:09:45
Block: 991545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208058 RingCT/type: yes/0
Extra: 0158a3c8d1bdcb099cb83da49e1bdd6a8dcffae5ab446611c314dc281627eae9b60211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a85ad67488e3fdb48c808bb7847d567a7f38536c4caf34e20aa7da912f4cfdcd 0.600000000000 1451881 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": 991555, "vin": [ { "gen": { "height": 991545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a85ad67488e3fdb48c808bb7847d567a7f38536c4caf34e20aa7da912f4cfdcd" } } ], "extra": [ 1, 88, 163, 200, 209, 189, 203, 9, 156, 184, 61, 164, 158, 27, 221, 106, 141, 207, 250, 229, 171, 68, 102, 17, 195, 20, 220, 40, 22, 39, 234, 233, 182, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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