Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a940eb8e99770a6daeacbe9355bdf96902810cc374efb257d4e099f32c621e0

Tx prefix hash: afc6aaede07b3bd27d28b08c8aa106511baa75e2471c1ebc954d72ff88d1ddc8
Tx public key: b52ab8a736de9317e91533604cad26d8da05f31240f3acf7ddad053008e74f7e
Timestamp: 1729018836 Timestamp [UCT]: 2024-10-15 19:00:36 Age [y:d:h:m:s]: 00:174:18:38:08
Block: 1132333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124681 RingCT/type: yes/0
Extra: 01b52ab8a736de9317e91533604cad26d8da05f31240f3acf7ddad053008e74f7e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e9823f73ade99a2074853b3f23d65662341cbdee373b1d6b52c3a75a9b485b6 0.600000000000 1615246 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": 1132343, "vin": [ { "gen": { "height": 1132333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e9823f73ade99a2074853b3f23d65662341cbdee373b1d6b52c3a75a9b485b6" } } ], "extra": [ 1, 181, 42, 184, 167, 54, 222, 147, 23, 233, 21, 51, 96, 76, 173, 38, 216, 218, 5, 243, 18, 64, 243, 172, 247, 221, 173, 5, 48, 8, 231, 79, 126, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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