Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 920cb4e11cdcc7670e5b1a74cd74cd68e6dd7cb6f49fba56ab422aaf0948c3c8

Tx prefix hash: 997ab47ca31d4da0f65bb8c1c9d12dfefb94ca31dd3116feb9a0c82eec5be077
Tx public key: b7dd654a8fae609e9fd0e8ed11a4e64208517a8905d4c14cc7b52747340b36f3
Timestamp: 1717324586 Timestamp [UCT]: 2024-06-02 10:36:26 Age [y:d:h:m:s]: 00:347:11:08:51
Block: 1035383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248347 RingCT/type: yes/0
Extra: 01b7dd654a8fae609e9fd0e8ed11a4e64208517a8905d4c14cc7b52747340b36f302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f1f746ed56596b1744cb3ce1508ef838d0f1e1aff47904e339ae1c7e681b80 0.600000000000 1503904 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": 1035393, "vin": [ { "gen": { "height": 1035383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f1f746ed56596b1744cb3ce1508ef838d0f1e1aff47904e339ae1c7e681b80" } } ], "extra": [ 1, 183, 221, 101, 74, 143, 174, 96, 158, 159, 208, 232, 237, 17, 164, 230, 66, 8, 81, 122, 137, 5, 212, 193, 76, 199, 181, 39, 71, 52, 11, 54, 243, 2, 17, 0, 0, 0, 2, 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