Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635dba911f087cb83f4a37b884dc0c2ed716a380902789bbc6f8c0727e3434f2

Tx prefix hash: d8751a4f220f36a4d2deb4591d0556559c69512ba1b58bd62cb01a7535d93b2a
Tx public key: e562218423bfc461ecea9720cc46728271e704ed936407a79a3c9f9dcd61ed7b
Timestamp: 1708517913 Timestamp [UCT]: 2024-02-21 12:18:33 Age [y:d:h:m:s]: 00:266:21:08:16
Block: 962369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191064 RingCT/type: yes/0
Extra: 01e562218423bfc461ecea9720cc46728271e704ed936407a79a3c9f9dcd61ed7b021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 322db0a531a9c89c15d0d7e0cf5b5cee8625b5446023400efb530cc9a4f81810 0.600000000000 1422002 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": 962379, "vin": [ { "gen": { "height": 962369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "322db0a531a9c89c15d0d7e0cf5b5cee8625b5446023400efb530cc9a4f81810" } } ], "extra": [ 1, 229, 98, 33, 132, 35, 191, 196, 97, 236, 234, 151, 32, 204, 70, 114, 130, 113, 231, 4, 237, 147, 100, 7, 167, 154, 60, 159, 157, 205, 97, 237, 123, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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