Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669b20746d91c8cca60f60c7da766ac014b4682918c7a6bb0d562ec1bb92717c

Tx prefix hash: 474bbe036044e0dbd4982adb660ee321e48e01b6d1aab90559c1c13435b8a5f5
Tx public key: b7e8747977584a0df810cfd0b2bd4ed3f4c931fd69e6c4dceb70736c8eabb2c8
Timestamp: 1607979486 Timestamp [UCT]: 2020-12-14 20:58:06 Age [y:d:h:m:s]: 04:044:04:05:36
Block: 162114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043803 RingCT/type: yes/0
Extra: 01b7e8747977584a0df810cfd0b2bd4ed3f4c931fd69e6c4dceb70736c8eabb2c802110000003f27e2517e000000000000000000

1 output(s) for total of 178.182362546000 dcy

stealth address amount amount idx
00: 18a0cefb4dcf7b7495784516987a07f2a6d6bd5585c3f2ee1f8322421bf6184d 178.182362546000 288755 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": 162124, "vin": [ { "gen": { "height": 162114 } } ], "vout": [ { "amount": 178182362546, "target": { "key": "18a0cefb4dcf7b7495784516987a07f2a6d6bd5585c3f2ee1f8322421bf6184d" } } ], "extra": [ 1, 183, 232, 116, 121, 119, 88, 74, 13, 248, 16, 207, 208, 178, 189, 78, 211, 244, 201, 49, 253, 105, 230, 196, 220, 235, 112, 115, 108, 142, 171, 178, 200, 2, 17, 0, 0, 0, 63, 39, 226, 81, 126, 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