Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ace5e6c7983215c480a22c66f96183faa02eb1780a68d9e206ece979dabd33

Tx prefix hash: d7a1a026927a657fc2f72159cf3dd941f2438cc2f6abe3cb714711fc7f6db5f5
Tx public key: a85e7d6881242cd92c9a0da46f53564856dad4e8610d9d2d6bd271b4d1c8929a
Timestamp: 1734342189 Timestamp [UCT]: 2024-12-16 09:43:09 Age [y:d:h:m:s]: 00:093:01:55:48
Block: 1176370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66305 RingCT/type: yes/0
Extra: 01a85e7d6881242cd92c9a0da46f53564856dad4e8610d9d2d6bd271b4d1c8929a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44fad2f62c1431ec6c7f7c25e0dead1f76ece0c9f58c2bac70da93ba04579489 0.600000000000 1662701 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": 1176380, "vin": [ { "gen": { "height": 1176370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44fad2f62c1431ec6c7f7c25e0dead1f76ece0c9f58c2bac70da93ba04579489" } } ], "extra": [ 1, 168, 94, 125, 104, 129, 36, 44, 217, 44, 154, 13, 164, 111, 83, 86, 72, 86, 218, 212, 232, 97, 13, 157, 45, 107, 210, 113, 180, 209, 200, 146, 154, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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