Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367de3609a8510dd2b61c9427a4662f8585361bd10fc73061abb5085efcc8c2c

Tx prefix hash: 9caafec268746fe5c29c99d0fcb251b45b2fa2c949c61d637098e2ab4dcd419a
Tx public key: 7b2eb9c41fcdb2c78662c92bfd03bd0be695e26dc0b4bfa9a5001d23096b7f0b
Timestamp: 1709363797 Timestamp [UCT]: 2024-03-02 07:16:37 Age [y:d:h:m:s]: 01:062:23:04:03
Block: 969383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306017 RingCT/type: yes/0
Extra: 017b2eb9c41fcdb2c78662c92bfd03bd0be695e26dc0b4bfa9a5001d23096b7f0b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebe243c77c87320b3abc10573c02e146a526e3cfb82ca7efcdd80a136509b51c 0.600000000000 1429212 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": 969393, "vin": [ { "gen": { "height": 969383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebe243c77c87320b3abc10573c02e146a526e3cfb82ca7efcdd80a136509b51c" } } ], "extra": [ 1, 123, 46, 185, 196, 31, 205, 178, 199, 134, 98, 201, 43, 253, 3, 189, 11, 230, 149, 226, 109, 192, 180, 191, 169, 165, 0, 29, 35, 9, 107, 127, 11, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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