Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559f0fd26d50dbf58ae44d10ac1be370e5b28ca27071df5ee399763faa53b311

Tx prefix hash: bc7545946abd7cf5e1a029b9313c146d0559088e28856ecb57a0b8fcd1fdc74c
Tx public key: 2c8993f04adc4586115bbebaca61c5daac97ee6b66c85971ec33c8ebd959f79d
Timestamp: 1699290462 Timestamp [UCT]: 2023-11-06 17:07:42 Age [y:d:h:m:s]: 01:153:01:54:46
Block: 885863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370594 RingCT/type: yes/0
Extra: 012c8993f04adc4586115bbebaca61c5daac97ee6b66c85971ec33c8ebd959f79d021100000006faf35c9c000000000000000000

1 output(s) for total of 0.712472565000 dcy

stealth address amount amount idx
00: 328975fdff1e83662fdc7b51bce4dcee5caed1b669f1cf6b0e92aa391af30fdf 0.712472565000 1341656 of 0

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": 885873, "vin": [ { "gen": { "height": 885863 } } ], "vout": [ { "amount": 712472565, "target": { "key": "328975fdff1e83662fdc7b51bce4dcee5caed1b669f1cf6b0e92aa391af30fdf" } } ], "extra": [ 1, 44, 137, 147, 240, 74, 220, 69, 134, 17, 91, 190, 186, 202, 97, 197, 218, 172, 151, 238, 107, 102, 200, 89, 113, 236, 51, 200, 235, 217, 89, 247, 157, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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