Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f5544dd3f9ba3b50c08615fd2c881b9ee0128795360a3ebec49067f5a9fd99f

Tx prefix hash: 33356c0d05b09a02719e18df03518ef51258d6b9f290b6717421dae768d33953
Tx public key: ba93552bd76a5b39b64ad335ad7fd636adf39f0491902ba6d7d41c7ff7131394
Timestamp: 1705256416 Timestamp [UCT]: 2024-01-14 18:20:16 Age [y:d:h:m:s]: 01:084:17:55:53
Block: 935314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321652 RingCT/type: yes/0
Extra: 01ba93552bd76a5b39b64ad335ad7fd636adf39f0491902ba6d7d41c7ff713139402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e8c7e56f383f97567984b7d4d2943081cff2dcacc07565f5823026f4efa5f0a 0.600000000000 1393330 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": 935324, "vin": [ { "gen": { "height": 935314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e8c7e56f383f97567984b7d4d2943081cff2dcacc07565f5823026f4efa5f0a" } } ], "extra": [ 1, 186, 147, 85, 43, 215, 106, 91, 57, 182, 74, 211, 53, 173, 127, 214, 54, 173, 243, 159, 4, 145, 144, 43, 166, 215, 212, 28, 127, 247, 19, 19, 148, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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