Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03ec33be898531b931d8a0835c0faaa0a42b4bcff7e1dbb31e5ecd29e7eb34f9

Tx prefix hash: 7b6278ebefd5b6c793309de4f0ee064da69ed3271d6e30d616c627796f305c03
Tx public key: a713b2ca3dc61e87be0068d5f8b1848386a791d44ddb54ff76b75d0105a59990
Timestamp: 1731154019 Timestamp [UCT]: 2024-11-09 12:06:59 Age [y:d:h:m:s]: 00:125:03:55:58
Block: 1149940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89292 RingCT/type: yes/0
Extra: 01a713b2ca3dc61e87be0068d5f8b1848386a791d44ddb54ff76b75d0105a59990021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74611b212019e5ed774ee6afe9758efc8762a6900fc65d5257d0df0b90f850f1 0.600000000000 1635121 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": 1149950, "vin": [ { "gen": { "height": 1149940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74611b212019e5ed774ee6afe9758efc8762a6900fc65d5257d0df0b90f850f1" } } ], "extra": [ 1, 167, 19, 178, 202, 61, 198, 30, 135, 190, 0, 104, 213, 248, 177, 132, 131, 134, 167, 145, 212, 77, 219, 84, 255, 118, 183, 93, 1, 5, 165, 153, 144, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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