Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1df1e80760e842b6b2b9e5fe9495bdeb570485de81ecd35e131e9eddf239764d

Tx prefix hash: 793cb5e0aad8eed235ebc2fb74cab6266e3a41dc919dfbf956651637e60ca242
Tx public key: c01fd552aba059b9bfbe26e6e911d8e18fbae6ff64e4a0a5b427a7db1effe4c7
Timestamp: 1732402615 Timestamp [UCT]: 2024-11-23 22:56:55 Age [y:d:h:m:s]: 00:209:11:00:14
Block: 1160284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149393 RingCT/type: yes/0
Extra: 01c01fd552aba059b9bfbe26e6e911d8e18fbae6ff64e4a0a5b427a7db1effe4c70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571e3fb4eabff4bddb8ea3312eb8d2adba4d6d6c9bf1e8d328f74c97d1b666e2 0.600000000000 1645929 of 15

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": 1160294, "vin": [ { "gen": { "height": 1160284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571e3fb4eabff4bddb8ea3312eb8d2adba4d6d6c9bf1e8d328f74c97d1b666e2" } } ], "extra": [ 1, 192, 31, 213, 82, 171, 160, 89, 185, 191, 190, 38, 230, 233, 17, 216, 225, 143, 186, 230, 255, 100, 228, 160, 165, 180, 39, 167, 219, 30, 255, 228, 199, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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