Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a163764e59f1d3afd02c1485d611eacc0b9090a3c2bb320e379c6ce04f2ff60

Tx prefix hash: 14e568ab8af836162f3cbb73be20e6affb3d7289745a1419b1966ac1b997e528
Tx public key: 0dc5f96edd226e8b56f0752b9e66d51440578e3d5bae33c57ba7b754f904575b
Timestamp: 1703959011 Timestamp [UCT]: 2023-12-30 17:56:51 Age [y:d:h:m:s]: 01:136:18:05:00
Block: 924557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358884 RingCT/type: yes/0
Extra: 010dc5f96edd226e8b56f0752b9e66d51440578e3d5bae33c57ba7b754f904575b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699b1767800c8e46aed884244e11cc9ab4a0083adb96a89f7822a0ae80c35ed0 0.600000000000 1382311 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": 924567, "vin": [ { "gen": { "height": 924557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699b1767800c8e46aed884244e11cc9ab4a0083adb96a89f7822a0ae80c35ed0" } } ], "extra": [ 1, 13, 197, 249, 110, 221, 34, 110, 139, 86, 240, 117, 43, 158, 102, 213, 20, 64, 87, 142, 61, 91, 174, 51, 197, 123, 167, 183, 84, 249, 4, 87, 91, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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