Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5df13c6114d12a12974305162985f83378d2461440746fbedba3a82035f4ff5e

Tx prefix hash: f6129d20e3cb70404a8b67057bae6695e995e31ed551f9c78f7d045b27e35eb2
Tx public key: a7969eebbb7a2c393107cfd4d49ef5ee291cceb6f78d2b918ee2e87ba53bae36
Timestamp: 1713445784 Timestamp [UCT]: 2024-04-18 13:09:44 Age [y:d:h:m:s]: 00:210:19:27:05
Block: 1003201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150924 RingCT/type: yes/0
Extra: 01a7969eebbb7a2c393107cfd4d49ef5ee291cceb6f78d2b918ee2e87ba53bae3602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd83aed31094f68eeb9e1244830ec4b146a68e9e261babc943c6c2ce4d057c9 0.600000000000 1463731 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": 1003211, "vin": [ { "gen": { "height": 1003201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd83aed31094f68eeb9e1244830ec4b146a68e9e261babc943c6c2ce4d057c9" } } ], "extra": [ 1, 167, 150, 158, 235, 187, 122, 44, 57, 49, 7, 207, 212, 212, 158, 245, 238, 41, 28, 206, 182, 247, 141, 43, 145, 142, 226, 232, 123, 165, 59, 174, 54, 2, 17, 0, 0, 0, 6, 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