Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 285331e6e19745ee2c57470c6cf7c5c72b68a030113c2afe4596893cba8f47df

Tx prefix hash: cf5e234048d84ffac021b604aa8991504a2ad99e471c82873f0d0af7a4e3a3f5
Tx public key: af3941f24ace887e6f18c397e822110a8d7ba0d433a2dbeef3c14dd9f359b7b8
Timestamp: 1737232335 Timestamp [UCT]: 2025-01-18 20:32:15 Age [y:d:h:m:s]: 00:151:03:14:53
Block: 1200234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107741 RingCT/type: yes/0
Extra: 01af3941f24ace887e6f18c397e822110a8d7ba0d433a2dbeef3c14dd9f359b7b8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f773ec7aba9e1ce256a3155d99753dc96ce155435fb3f3dae0d958023ba69638 0.600000000000 1686877 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": 1200244, "vin": [ { "gen": { "height": 1200234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f773ec7aba9e1ce256a3155d99753dc96ce155435fb3f3dae0d958023ba69638" } } ], "extra": [ 1, 175, 57, 65, 242, 74, 206, 136, 126, 111, 24, 195, 151, 232, 34, 17, 10, 141, 123, 160, 212, 51, 162, 219, 238, 243, 193, 77, 217, 243, 89, 183, 184, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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