Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b66d4ec7473c38be1f904cd6082357a8d510575e8045732423cd2be4ada80a

Tx prefix hash: 3a05e0d506591ee0dd319f6b10c154427cfc0499d21373b360af6e416240ac1d
Tx public key: 7da31f8574f4cd0ef076a4edce202c92c0541979484a5168e4a6ee72e354d0a7
Timestamp: 1581364891 Timestamp [UCT]: 2020-02-10 20:01:31 Age [y:d:h:m:s]: 04:364:22:54:57
Block: 62253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152730 RingCT/type: yes/0
Extra: 017da31f8574f4cd0ef076a4edce202c92c0541979484a5168e4a6ee72e354d0a702110000010912c4732d000000000000000000

1 output(s) for total of 381.707579357000 dcy

stealth address amount amount idx
00: 64fa2c5591c7bce7c1c61face73e7e62705957ba01fae0c039814c09473eb666 381.707579357000 114812 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": 62263, "vin": [ { "gen": { "height": 62253 } } ], "vout": [ { "amount": 381707579357, "target": { "key": "64fa2c5591c7bce7c1c61face73e7e62705957ba01fae0c039814c09473eb666" } } ], "extra": [ 1, 125, 163, 31, 133, 116, 244, 205, 14, 240, 118, 164, 237, 206, 32, 44, 146, 192, 84, 25, 121, 72, 74, 81, 104, 228, 166, 238, 114, 227, 84, 208, 167, 2, 17, 0, 0, 1, 9, 18, 196, 115, 45, 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