Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9af2a2d410787e3144c6e0d98682814569694eb6cd3459d7e28d86ab7096fbd

Tx prefix hash: 0c595c8e3afec169e3b56dfbbf09553cc4d7b77dc367eccaa0d113dcad1d1f7f
Tx public key: 9fe5e2d1c1cfe03484a68ed22d8324b32bb3c5e8843c964d32360345655e07c0
Timestamp: 1675573118 Timestamp [UCT]: 2023-02-05 04:58:38 Age [y:d:h:m:s]: 02:097:09:14:00
Block: 690117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591239 RingCT/type: yes/0
Extra: 019fe5e2d1c1cfe03484a68ed22d8324b32bb3c5e8843c964d32360345655e07c00211000000017e406890000000000000000000

1 output(s) for total of 3.172165413000 dcy

stealth address amount amount idx
00: 549b3ff07b9f864766610fd61d719221389a17b803512fcf6c44a3351019b3d1 3.172165413000 1132823 of 0

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": 690127, "vin": [ { "gen": { "height": 690117 } } ], "vout": [ { "amount": 3172165413, "target": { "key": "549b3ff07b9f864766610fd61d719221389a17b803512fcf6c44a3351019b3d1" } } ], "extra": [ 1, 159, 229, 226, 209, 193, 207, 224, 52, 132, 166, 142, 210, 45, 131, 36, 179, 43, 179, 197, 232, 132, 60, 150, 77, 50, 54, 3, 69, 101, 94, 7, 192, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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