Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20aa43430f29cb9a6f401e35e3f2cf5d3d55e6c48770bd42a47a2aed501826fb

Tx prefix hash: e2c19664bc73004934eb4deed6ca64de6a390cd211ec360afcc76be505fe8b86
Tx public key: c185bef6a01e88f8f45ef8fb80e17bd79e27d78b98102f5116fdd8b8984e5a6f
Timestamp: 1765552293 Timestamp [UCT]: 2025-12-12 15:11:33 Age [y:d:h:m:s]: 00:025:15:18:26
Block: 1432074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18357 RingCT/type: yes/0
Extra: 01c185bef6a01e88f8f45ef8fb80e17bd79e27d78b98102f5116fdd8b8984e5a6f021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c9618f850d886742c3ba83b13cfdb2b9cad1315d459b9484e46664c5768ccb6 0.600000000000 1920853 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": 1432084, "vin": [ { "gen": { "height": 1432074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c9618f850d886742c3ba83b13cfdb2b9cad1315d459b9484e46664c5768ccb6" } } ], "extra": [ 1, 193, 133, 190, 246, 160, 30, 136, 248, 244, 94, 248, 251, 128, 225, 123, 215, 158, 39, 215, 139, 152, 16, 47, 81, 22, 253, 216, 184, 152, 78, 90, 111, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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