Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d9c2b44b91e5711c8828f437656043dce5c0cee659377b1c152e6c9e5183166

Tx prefix hash: dba9a79f5e7516798546c5f26169ced240ec8b83347e7fe6f031a43d10ac31af
Tx public key: 6d89281a21ab01c34bff7b3deb21603e1f0c2011156eec08313d1d2eb300cb6c
Timestamp: 1726217757 Timestamp [UCT]: 2024-09-13 08:55:57 Age [y:d:h:m:s]: 00:241:13:51:43
Block: 1109101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172508 RingCT/type: yes/0
Extra: 016d89281a21ab01c34bff7b3deb21603e1f0c2011156eec08313d1d2eb300cb6c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c505e9212efc7807b0e612d70bca5798b188baf8a2b2fcb4ad487299203878 0.600000000000 1587234 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": 1109111, "vin": [ { "gen": { "height": 1109101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c505e9212efc7807b0e612d70bca5798b188baf8a2b2fcb4ad487299203878" } } ], "extra": [ 1, 109, 137, 40, 26, 33, 171, 1, 195, 75, 255, 123, 61, 235, 33, 96, 62, 31, 12, 32, 17, 21, 110, 236, 8, 49, 61, 29, 46, 179, 0, 203, 108, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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