Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d45ae2025f99fa863494b04ec5ef9473e44c889c29a856adb770677677ac7e05

Tx prefix hash: 264bec7d6721f0e49992812f5d71f8696cad7a87970b0db374af26fced799cb6
Tx public key: fb6c905cb751ce4d12b0c5325c385d2a685083b550c4b4ea8c58f50910f6525c
Timestamp: 1703431017 Timestamp [UCT]: 2023-12-24 15:16:57 Age [y:d:h:m:s]: 01:128:20:39:13
Block: 920191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353220 RingCT/type: yes/0
Extra: 01fb6c905cb751ce4d12b0c5325c385d2a685083b550c4b4ea8c58f50910f6525c021100000001ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0015d856b0b3017aeb7b5e45f5fd0533d599ef5e7165216667216f332985eac7 0.600000000000 1377869 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": 920201, "vin": [ { "gen": { "height": 920191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0015d856b0b3017aeb7b5e45f5fd0533d599ef5e7165216667216f332985eac7" } } ], "extra": [ 1, 251, 108, 144, 92, 183, 81, 206, 77, 18, 176, 197, 50, 92, 56, 93, 42, 104, 80, 131, 181, 80, 196, 180, 234, 140, 88, 245, 9, 16, 246, 82, 92, 2, 17, 0, 0, 0, 1, 173, 86, 148, 172, 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