Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22d82d9c76406a59d5d94a854c66ddfc680a460efc3c1a136abbd64d1c13dbfe

Tx prefix hash: 172770ee31737a9b77d0cb6c109ecb75320f0e9305e31d1e2a7a5577b04a8f6c
Tx public key: b6674648a02a073ff845fa7540d89628327150b9e6f3c0fc3d8d1383a4754523
Timestamp: 1708705942 Timestamp [UCT]: 2024-02-23 16:32:22 Age [y:d:h:m:s]: 01:259:10:17:21
Block: 963925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444147 RingCT/type: yes/0
Extra: 01b6674648a02a073ff845fa7540d89628327150b9e6f3c0fc3d8d1383a47545230211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94c1ee837372993831d407e6798a58563cb89bf40c199daf043859cb8404cee8 0.600000000000 1423652 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": 963935, "vin": [ { "gen": { "height": 963925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94c1ee837372993831d407e6798a58563cb89bf40c199daf043859cb8404cee8" } } ], "extra": [ 1, 182, 103, 70, 72, 160, 42, 7, 63, 248, 69, 250, 117, 64, 216, 150, 40, 50, 113, 80, 185, 230, 243, 192, 252, 61, 141, 19, 131, 164, 117, 69, 35, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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