Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3095db497c8357800af6666b1b4eab0a55d08cc898fba38c0950b9a32667981c

Tx prefix hash: fe8a631a23fb277403456fe291c924d2d65f702cd2fb5461646d3e6d78b5d769
Tx public key: 6faec87b3de5150a4dad27ce7bca9bdf51ae50ddfb57c1f79aff8de20d9d6308
Timestamp: 1696760454 Timestamp [UCT]: 2023-10-08 10:20:54 Age [y:d:h:m:s]: 01:247:10:27:15
Block: 865096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437902 RingCT/type: yes/0
Extra: 016faec87b3de5150a4dad27ce7bca9bdf51ae50ddfb57c1f79aff8de20d9d630802110000000136a45730000000000000000000

1 output(s) for total of 0.834791211000 dcy

stealth address amount amount idx
00: 66f1e2b0a9ec169d5a56bdaf8389946cf2c6cec7c69cb4c70af435556af0180b 0.834791211000 1319622 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": 865106, "vin": [ { "gen": { "height": 865096 } } ], "vout": [ { "amount": 834791211, "target": { "key": "66f1e2b0a9ec169d5a56bdaf8389946cf2c6cec7c69cb4c70af435556af0180b" } } ], "extra": [ 1, 111, 174, 200, 123, 61, 229, 21, 10, 77, 173, 39, 206, 123, 202, 155, 223, 81, 174, 80, 221, 251, 87, 193, 247, 154, 255, 141, 226, 13, 157, 99, 8, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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