Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ee22dc5ec617ffa377f64146154883d24541c57301b2bd6f6e6944e4b7b23ca

Tx prefix hash: d481233a574c7831fc249bef33fd0ebc3c3b313410baadb14cefd48dc8041569
Tx public key: da2a649d336f357ba1f8f4a233f1518cd20c7d371080329b50f0fe0e9b0eac9e
Timestamp: 1751761454 Timestamp [UCT]: 2025-07-06 00:24:14 Age [y:d:h:m:s]: 00:138:03:39:02
Block: 1319579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97112 RingCT/type: yes/0
Extra: 01da2a649d336f357ba1f8f4a233f1518cd20c7d371080329b50f0fe0e9b0eac9e021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c6cddb18e5d0a82e730418ee54ff1175a3cb157add03821749361f0f1d55b8d 0.600000000000 1807272 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": 1319589, "vin": [ { "gen": { "height": 1319579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c6cddb18e5d0a82e730418ee54ff1175a3cb157add03821749361f0f1d55b8d" } } ], "extra": [ 1, 218, 42, 100, 157, 51, 111, 53, 123, 161, 248, 244, 162, 51, 241, 81, 140, 210, 12, 125, 55, 16, 128, 50, 155, 80, 240, 254, 14, 155, 14, 172, 158, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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