Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e102cda692fcdfc3c1da6bd98c8cdcf0174da53754f63817aae00defec0e85

Tx prefix hash: fdc82aaf2c9b98ecaeb90fffdc8fb56e2bac46c92caa89dc619b7ae51e501e8c
Tx public key: 76237e5dd2be277d0a6569ce9532629e26167bfd43943ae1f0d028bd71f972c9
Timestamp: 1577460139 Timestamp [UCT]: 2019-12-27 15:22:19 Age [y:d:h:m:s]: 05:308:01:00:19
Block: 32924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367689 RingCT/type: yes/0
Extra: 0176237e5dd2be277d0a6569ce9532629e26167bfd43943ae1f0d028bd71f972c90211000001b2ac34bf9e000000000000000000

1 output(s) for total of 477.438530723000 dcy

stealth address amount amount idx
00: 3e6c48498e67e371f1ed112d666b1fa01b7c40654dc546466119314eab1d0e39 477.438530723000 54876 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": 32934, "vin": [ { "gen": { "height": 32924 } } ], "vout": [ { "amount": 477438530723, "target": { "key": "3e6c48498e67e371f1ed112d666b1fa01b7c40654dc546466119314eab1d0e39" } } ], "extra": [ 1, 118, 35, 126, 93, 210, 190, 39, 125, 10, 101, 105, 206, 149, 50, 98, 158, 38, 22, 123, 253, 67, 148, 58, 225, 240, 208, 40, 189, 113, 249, 114, 201, 2, 17, 0, 0, 1, 178, 172, 52, 191, 158, 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