Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c996594efb42c6275fd41ca61cdff4ef5960d58087ff4d6e8e1a82f59a874ef8

Tx prefix hash: deca55e1b194b6fe6d4ca879d07589dd41512367bd3e48e9f5e459be1e274a84
Tx public key: 69209e7e885ff0dcd0e349b9e3f74bab12488a591f1ee1bea8ba0161aaec8721
Timestamp: 1754260572 Timestamp [UCT]: 2025-08-03 22:36:12 Age [y:d:h:m:s]: 00:057:20:56:17
Block: 1339702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40218 RingCT/type: yes/0
Extra: 0169209e7e885ff0dcd0e349b9e3f74bab12488a591f1ee1bea8ba0161aaec872102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc2e425b4f6e8bb2d98218791081be16eb6cd29315a72d6dae4c3851065f2134 0.600000000000 1827517 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": 1339712, "vin": [ { "gen": { "height": 1339702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc2e425b4f6e8bb2d98218791081be16eb6cd29315a72d6dae4c3851065f2134" } } ], "extra": [ 1, 105, 32, 158, 126, 136, 95, 240, 220, 208, 227, 73, 185, 227, 247, 75, 171, 18, 72, 138, 89, 31, 30, 225, 190, 168, 186, 1, 97, 170, 236, 135, 33, 2, 17, 0, 0, 0, 1, 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