Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549d5d54581de94b5caddc83ef7ada1eb5a36b6d3f111e1de310a3b4aea50884

Tx prefix hash: 427022c7e54863933b7eecbb9aa919a3aa0eb90efd005eca4fb73f20d72d38ed
Tx public key: e2d302f778b10b97b1feb6ec44c7a1e3e2d272b265a13b0cf34ee14fe584ce0d
Timestamp: 1708114311 Timestamp [UCT]: 2024-02-16 20:11:51 Age [y:d:h:m:s]: 01:106:01:03:07
Block: 959013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336866 RingCT/type: yes/0
Extra: 01e2d302f778b10b97b1feb6ec44c7a1e3e2d272b265a13b0cf34ee14fe584ce0d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e2f2051bf23490c525e3aed1271ad1dc0cdfc6eefe2fc6f666a49478bc6bb69 0.600000000000 1418532 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": 959023, "vin": [ { "gen": { "height": 959013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e2f2051bf23490c525e3aed1271ad1dc0cdfc6eefe2fc6f666a49478bc6bb69" } } ], "extra": [ 1, 226, 211, 2, 247, 120, 177, 11, 151, 177, 254, 182, 236, 68, 199, 161, 227, 226, 210, 114, 178, 101, 161, 59, 12, 243, 78, 225, 79, 229, 132, 206, 13, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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