Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bde0ca4b5e16f977870c303ea8ba79e29ac7fd8f8b90cd582b0632af202553c

Tx prefix hash: 2ffb55fd77bc80571b9d54d50e908e84d040722c5061b4fc52a0b95477bb1c21
Tx public key: f0f9fdad235d4dcb009fd8985d9d58d76b53dc7641f01c33661eb93ba9131ad2
Timestamp: 1741350295 Timestamp [UCT]: 2025-03-07 12:24:55 Age [y:d:h:m:s]: 00:258:13:14:42
Block: 1234101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182517 RingCT/type: yes/0
Extra: 01f0f9fdad235d4dcb009fd8985d9d58d76b53dc7641f01c33661eb93ba9131ad20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9b6af7798d8ec26a3bd37ab15d72f049acbb332df33c47889ea0be528c0847f 0.600000000000 1721026 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": 1234111, "vin": [ { "gen": { "height": 1234101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9b6af7798d8ec26a3bd37ab15d72f049acbb332df33c47889ea0be528c0847f" } } ], "extra": [ 1, 240, 249, 253, 173, 35, 93, 77, 203, 0, 159, 216, 152, 93, 157, 88, 215, 107, 83, 220, 118, 65, 240, 28, 51, 102, 30, 185, 59, 169, 19, 26, 210, 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