Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39e6f8f6061b1afd6febc9b35bb008a2baf7f29c9765ba35064189e11dda615a

Tx prefix hash: 555472a133e96276c53d5e560647f0a98c3c44e13603c65edf86cb860110c3d1
Tx public key: 7997616ca2661b7c6b5e4b1c0d68e649d1bdd3180bbfdd48eac82c04bfd35eeb
Timestamp: 1708852614 Timestamp [UCT]: 2024-02-25 09:16:54 Age [y:d:h:m:s]: 01:113:05:09:22
Block: 965146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341862 RingCT/type: yes/0
Extra: 017997616ca2661b7c6b5e4b1c0d68e649d1bdd3180bbfdd48eac82c04bfd35eeb0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a02643ae69690f7222118bcfb4351535776c00c48af6a09bedbce0fbdb7709f1 0.600000000000 1424895 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": 965156, "vin": [ { "gen": { "height": 965146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a02643ae69690f7222118bcfb4351535776c00c48af6a09bedbce0fbdb7709f1" } } ], "extra": [ 1, 121, 151, 97, 108, 162, 102, 27, 124, 107, 94, 75, 28, 13, 104, 230, 73, 209, 189, 211, 24, 11, 191, 221, 72, 234, 200, 44, 4, 191, 211, 94, 235, 2, 17, 0, 0, 0, 5, 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