Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba9962c4e6bffafcf6023591b7c944b4ce8814c58eb6b65e93b1635841fe4dea

Tx prefix hash: 9e3a5ffde8af3ed31f91764dea071890248adc0ea008c19bbd387c3423343d64
Tx public key: e45262622a2d3e9e024d5ee88686550340b6bb9ec0b7cd1ef923a18c3251e31e
Timestamp: 1648279597 Timestamp [UCT]: 2022-03-26 07:26:37 Age [y:d:h:m:s]: 02:274:23:30:35
Block: 466634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716078 RingCT/type: yes/0
Extra: 01e45262622a2d3e9e024d5ee88686550340b6bb9ec0b7cd1ef923a18c3251e31e0211000000034a0f5013000000000000000000

1 output(s) for total of 17.452116500000 dcy

stealth address amount amount idx
00: 4f7ba5fa0c333e51cd5c8e8b88fdea83bf6ac8736f07a00067e20cd4b62ccfe2 17.452116500000 884983 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": 466644, "vin": [ { "gen": { "height": 466634 } } ], "vout": [ { "amount": 17452116500, "target": { "key": "4f7ba5fa0c333e51cd5c8e8b88fdea83bf6ac8736f07a00067e20cd4b62ccfe2" } } ], "extra": [ 1, 228, 82, 98, 98, 42, 45, 62, 158, 2, 77, 94, 232, 134, 134, 85, 3, 64, 182, 187, 158, 192, 183, 205, 30, 249, 35, 161, 140, 50, 81, 227, 30, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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