Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c7732628cc9024b5ddded6494a312d1a1d37bf1309dc69cf3ae19c9b2d1e605

Tx prefix hash: 0da3193e9f4e59cfe3bd2924923ec61b6ae69e64db975fce21a961728717392f
Tx public key: 0fdd2478b1f93a533d85de366a24442bb25ec6952c2938fddd4245bb2d5e3a9c
Timestamp: 1753234026 Timestamp [UCT]: 2025-07-23 01:27:06 Age [y:d:h:m:s]: 00:116:22:31:29
Block: 1331336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82382 RingCT/type: yes/0
Extra: 010fdd2478b1f93a533d85de366a24442bb25ec6952c2938fddd4245bb2d5e3a9c021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c46eba4705d8073d343e4bdb3f3f80724773bedc7bd698abb756a3df07f6be4 0.600000000000 1819131 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": 1331346, "vin": [ { "gen": { "height": 1331336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c46eba4705d8073d343e4bdb3f3f80724773bedc7bd698abb756a3df07f6be4" } } ], "extra": [ 1, 15, 221, 36, 120, 177, 249, 58, 83, 61, 133, 222, 54, 106, 36, 68, 43, 178, 94, 198, 149, 44, 41, 56, 253, 221, 66, 69, 187, 45, 94, 58, 156, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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