Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e2a94f82bf3593f5eed2d91e91cfa354fd2aa8d5733d0c691f7d2758d023c42

Tx prefix hash: cb3c013f0932c796769c77fa600dac13738d9e84968bd12767c3ba4be455a73c
Tx public key: d7bb6a5ff9e9c882eec456e6db6b3666eee9db10dec697ec3c1ca710676648da
Timestamp: 1752796246 Timestamp [UCT]: 2025-07-17 23:50:46 Age [y:d:h:m:s]: 00:034:18:42:35
Block: 1327744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23704 RingCT/type: yes/0
Extra: 01d7bb6a5ff9e9c882eec456e6db6b3666eee9db10dec697ec3c1ca710676648da02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 783295b0aadc84c2dcff82abd89373274372833a0d64438cb42c5130fef3d7c8 0.600000000000 1815503 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": 1327754, "vin": [ { "gen": { "height": 1327744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "783295b0aadc84c2dcff82abd89373274372833a0d64438cb42c5130fef3d7c8" } } ], "extra": [ 1, 215, 187, 106, 95, 249, 233, 200, 130, 238, 196, 86, 230, 219, 107, 54, 102, 238, 233, 219, 16, 222, 198, 151, 236, 60, 28, 167, 16, 103, 102, 72, 218, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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