Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea7f472ec18c4eeb53883b3162586fb11861fd56d650c49ac2464c5fbe2c44e

Tx prefix hash: 214a68daa4ad671c9604e720456a8ea4d256739fb4746abb0bd6088548c5e11f
Tx public key: 698836fbd2cc8a2e2cf343a2cf6dbd03504b3b93545979c7ab9476c3ab1c84e0
Timestamp: 1738123300 Timestamp [UCT]: 2025-01-29 04:01:40 Age [y:d:h:m:s]: 00:044:08:36:29
Block: 1207395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31737 RingCT/type: yes/0
Extra: 01698836fbd2cc8a2e2cf343a2cf6dbd03504b3b93545979c7ab9476c3ab1c84e00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0168aaa55490adf861f68df653295e508f633d6d5c1140ab6bcb964e6d39a466 0.600000000000 1694118 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": 1207405, "vin": [ { "gen": { "height": 1207395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0168aaa55490adf861f68df653295e508f633d6d5c1140ab6bcb964e6d39a466" } } ], "extra": [ 1, 105, 136, 54, 251, 210, 204, 138, 46, 44, 243, 67, 162, 207, 109, 189, 3, 80, 75, 59, 147, 84, 89, 121, 199, 171, 148, 118, 195, 171, 28, 132, 224, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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