Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79fe93165533d6eeb9017be6605a9a666557ea2d504eb9c9da8831a629ec637

Tx prefix hash: 0bbaedc9059ca5920068a744d33bda28b29aae06fb3625c97d8e12d52ca6709a
Tx public key: de2521a7b14bdee4b938be192a491b0a237a8da36022fa962a2c8bc4c4f2c458
Timestamp: 1706715840 Timestamp [UCT]: 2024-01-31 15:44:00 Age [y:d:h:m:s]: 01:076:16:07:00
Block: 947407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315873 RingCT/type: yes/0
Extra: 01de2521a7b14bdee4b938be192a491b0a237a8da36022fa962a2c8bc4c4f2c458021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e37027dd358ffd75033794ccb664746ee8a5dc58d0f081e5761234d2f4896649 0.600000000000 1405755 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": 947417, "vin": [ { "gen": { "height": 947407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e37027dd358ffd75033794ccb664746ee8a5dc58d0f081e5761234d2f4896649" } } ], "extra": [ 1, 222, 37, 33, 167, 177, 75, 222, 228, 185, 56, 190, 25, 42, 73, 27, 10, 35, 122, 141, 163, 96, 34, 250, 150, 42, 44, 139, 196, 196, 242, 196, 88, 2, 17, 0, 0, 0, 1, 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