Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf84cd7a10421689bd427c565e681d0cf6ae29b2dfa1cdb9ff1e4f4bc846b56f

Tx prefix hash: 54436aa33077eee7ab67d918c1ad4a93a5f2b0a9c64e7e15363fbc63c08e3968
Tx public key: c30b7a71445e15a3223379f5e94226dcfae17cfceff0a8c1fe657784b1b7b56a
Timestamp: 1761315600 Timestamp [UCT]: 2025-10-24 14:20:00 Age [y:d:h:m:s]: 00:075:07:30:56
Block: 1396969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53922 RingCT/type: yes/0
Extra: 01c30b7a71445e15a3223379f5e94226dcfae17cfceff0a8c1fe657784b1b7b56a021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 3d099c8c0b11394be3fd50af3d6de7818f4d2a226f572645430056c9945cbdcc 0.600200000000 1885258 of 0

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": 1396979, "vin": [ { "gen": { "height": 1396969 } } ], "vout": [ { "amount": 600200000, "target": { "key": "3d099c8c0b11394be3fd50af3d6de7818f4d2a226f572645430056c9945cbdcc" } } ], "extra": [ 1, 195, 11, 122, 113, 68, 94, 21, 163, 34, 51, 121, 245, 233, 66, 38, 220, 250, 225, 124, 252, 239, 240, 168, 193, 254, 101, 119, 132, 177, 183, 181, 106, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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