Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30dcbba050ac8b03444b344f693ddd091b875471fd1113b851a861258252c254

Tx prefix hash: 6ac2eaa5f1e4d637aa547122170e4e2f5e1216005cebdad21da97863277ce1c2
Tx public key: e6fe0ebf2dfee2df748ab152d9fc9bcfae3abc646d4228071e4344d5fe2a06af
Timestamp: 1707464874 Timestamp [UCT]: 2024-02-09 07:47:54 Age [y:d:h:m:s]: 01:130:09:30:41
Block: 953624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354169 RingCT/type: yes/0
Extra: 01e6fe0ebf2dfee2df748ab152d9fc9bcfae3abc646d4228071e4344d5fe2a06af02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bea9e206b7764038d92e9a243e60ec8da7705dc53b5a7c0442a62f67e1598301 0.600000000000 1412858 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": 953634, "vin": [ { "gen": { "height": 953624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bea9e206b7764038d92e9a243e60ec8da7705dc53b5a7c0442a62f67e1598301" } } ], "extra": [ 1, 230, 254, 14, 191, 45, 254, 226, 223, 116, 138, 177, 82, 217, 252, 155, 207, 174, 58, 188, 100, 109, 66, 40, 7, 30, 67, 68, 213, 254, 42, 6, 175, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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