Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc4d4ad5a18dccdc14aafa876f0c37b37ecd01b5d789c63685b29a7ff36f1d5

Tx prefix hash: f6f91ce0b85a4deb698e766b35e4d9b5eb7a77efbf60922ef42dd7229de3197c
Tx public key: 9efbfc01054724618b1c6c6f55394b55c53ed91862a6d67ce976bb2418f42fc8
Timestamp: 1735233900 Timestamp [UCT]: 2024-12-26 17:25:00 Age [y:d:h:m:s]: 00:172:18:40:28
Block: 1183724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123225 RingCT/type: yes/0
Extra: 019efbfc01054724618b1c6c6f55394b55c53ed91862a6d67ce976bb2418f42fc80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b354376f4903cd9cbd14f982ea143e785c6a8f8aac8aef17bb08b74e13c479a 0.600000000000 1670173 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": 1183734, "vin": [ { "gen": { "height": 1183724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b354376f4903cd9cbd14f982ea143e785c6a8f8aac8aef17bb08b74e13c479a" } } ], "extra": [ 1, 158, 251, 252, 1, 5, 71, 36, 97, 139, 28, 108, 111, 85, 57, 75, 85, 197, 62, 217, 24, 98, 166, 214, 124, 233, 118, 187, 36, 24, 244, 47, 200, 2, 17, 0, 0, 0, 2, 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