Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c66cb975003589cd4b544582b410e38f7b7ccb310d3d1bb0961ccc3eba68919

Tx prefix hash: 5ebc908b13da5a3bac933007c0ac2dfaee7caf334bb4d35835c09031e6021607
Tx public key: 4e42832af418beb9ea2f3fda189e615a513994c2958f77cc5b6e552b4c4f6af2
Timestamp: 1763344217 Timestamp [UCT]: 2025-11-17 01:50:17 Age [y:d:h:m:s]: 00:011:05:13:57
Block: 1413768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8037 RingCT/type: yes/0
Extra: 014e42832af418beb9ea2f3fda189e615a513994c2958f77cc5b6e552b4c4f6af202110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170512a2c31aca856f73f6366c56b4cf9a9be7d26ade31afe44c10240d2b184a 0.600000000000 1902249 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": 1413778, "vin": [ { "gen": { "height": 1413768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170512a2c31aca856f73f6366c56b4cf9a9be7d26ade31afe44c10240d2b184a" } } ], "extra": [ 1, 78, 66, 131, 42, 244, 24, 190, 185, 234, 47, 63, 218, 24, 158, 97, 90, 81, 57, 148, 194, 149, 143, 119, 204, 91, 110, 85, 43, 76, 79, 106, 242, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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