Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a02909c9c0d99c36935127f7c8535369cf7144422a0c87f6bdde6cf1f183e3e

Tx prefix hash: 5cfca58bc18fd9c5feadc64ec0d92030495a44048bcdad1c846dfc80f62d1ae8
Tx public key: 0d7c1a3c23c4e1f532a18941b19a2c2b37de51799e32b79674cfde105b12001b
Timestamp: 1733201455 Timestamp [UCT]: 2024-12-03 04:50:55 Age [y:d:h:m:s]: 00:120:10:51:58
Block: 1166902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85891 RingCT/type: yes/0
Extra: 010d7c1a3c23c4e1f532a18941b19a2c2b37de51799e32b79674cfde105b12001b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1a59236d11d46049c774879b32e89a9f754eafa740d7c794491406d57ca08f 0.600000000000 1652595 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": 1166912, "vin": [ { "gen": { "height": 1166902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1a59236d11d46049c774879b32e89a9f754eafa740d7c794491406d57ca08f" } } ], "extra": [ 1, 13, 124, 26, 60, 35, 196, 225, 245, 50, 161, 137, 65, 177, 154, 44, 43, 55, 222, 81, 121, 158, 50, 183, 150, 116, 207, 222, 16, 91, 18, 0, 27, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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