Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c1e4710f224b2b169f1b92f9b87aa89070f54bf22c23b6249472d8f888d659

Tx prefix hash: 0bafff452c9c28cc3e90017096bbb1ef1ed15fa2bb2a7c031203e72bdcf72641
Tx public key: 6a30393cfe796738e4e0c374c3ce72c3537273340c2adf0db3dfe274ddf9b3fa
Timestamp: 1581269294 Timestamp [UCT]: 2020-02-09 17:28:14 Age [y:d:h:m:s]: 05:243:16:10:18
Block: 61622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1324459 RingCT/type: yes/0
Extra: 016a30393cfe796738e4e0c374c3ce72c3537273340c2adf0db3dfe274ddf9b3fa0211000000074ac5aa02000000000000000000

1 output(s) for total of 383.556243499000 dcy

stealth address amount amount idx
00: 262e240a6136eb14b279265f89cfbf812f9886b3f3d3e90c73ff5ba58e538fd2 383.556243499000 113588 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": 61632, "vin": [ { "gen": { "height": 61622 } } ], "vout": [ { "amount": 383556243499, "target": { "key": "262e240a6136eb14b279265f89cfbf812f9886b3f3d3e90c73ff5ba58e538fd2" } } ], "extra": [ 1, 106, 48, 57, 60, 254, 121, 103, 56, 228, 224, 195, 116, 195, 206, 114, 195, 83, 114, 115, 52, 12, 42, 223, 13, 179, 223, 226, 116, 221, 249, 179, 250, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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