Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0b68d1aabf35372970fdb05e31e0379776acf7e23b59b195ff5c45a4e6c65d

Tx prefix hash: 397e9f2526e266b46b555ed938d6746feeec1fc6bc4ddee49ce30cee2fd6353c
Tx public key: cc4e27374947de41137dab00a3977c8ef0990b620ce3f4c3035e78afe5e9b4f7
Timestamp: 1601229790 Timestamp [UCT]: 2020-09-27 18:03:10 Age [y:d:h:m:s]: 04:110:05:09:46
Block: 137596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1059892 RingCT/type: yes/0
Extra: 01cc4e27374947de41137dab00a3977c8ef0990b620ce3f4c3035e78afe5e9b4f70211000012363a3a2186000000000000000000

1 output(s) for total of 214.826593065000 dcy

stealth address amount amount idx
00: 615c7cb1d6f613c2d05612437980c4d5b4bac96fb5327ff97fd32e084b3d2715 214.826593065000 228951 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": 137606, "vin": [ { "gen": { "height": 137596 } } ], "vout": [ { "amount": 214826593065, "target": { "key": "615c7cb1d6f613c2d05612437980c4d5b4bac96fb5327ff97fd32e084b3d2715" } } ], "extra": [ 1, 204, 78, 39, 55, 73, 71, 222, 65, 19, 125, 171, 0, 163, 151, 124, 142, 240, 153, 11, 98, 12, 227, 244, 195, 3, 94, 120, 175, 229, 233, 180, 247, 2, 17, 0, 0, 18, 54, 58, 58, 33, 134, 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