Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeef45b471bf9cbedaed7649059098195595909273abec6ebba6006202c6a930

Tx prefix hash: 1e67ef45cc22cdfb2bd8c3a5882b369999a1a9c536cef33edc530d83b6d3c604
Tx public key: f36c965e4965747bbbeaa0ef120affa58da82067582a1f36afd28f743f7ae15f
Timestamp: 1581119744 Timestamp [UCT]: 2020-02-07 23:55:44 Age [y:d:h:m:s]: 04:294:20:35:14
Block: 60791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102279 RingCT/type: yes/0
Extra: 01f36c965e4965747bbbeaa0ef120affa58da82067582a1f36afd28f743f7ae15f02110000005d8a2ee0d9000000000000000000

1 output(s) for total of 385.989062569000 dcy

stealth address amount amount idx
00: 0e3d5e7ad2b6371af183ca4f97ea7fc6923b3e78b2f21945ae4834399fb89d51 385.989062569000 111968 of 0

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": 60801, "vin": [ { "gen": { "height": 60791 } } ], "vout": [ { "amount": 385989062569, "target": { "key": "0e3d5e7ad2b6371af183ca4f97ea7fc6923b3e78b2f21945ae4834399fb89d51" } } ], "extra": [ 1, 243, 108, 150, 94, 73, 101, 116, 123, 187, 234, 160, 239, 18, 10, 255, 165, 141, 168, 32, 103, 88, 42, 31, 54, 175, 210, 143, 116, 63, 122, 225, 95, 2, 17, 0, 0, 0, 93, 138, 46, 224, 217, 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