Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9434456426d9a7a4a608d8b513938954e70ac61f8e470d7cda327f4d96c2472c

Tx prefix hash: a9438c477249295bcbbdd5b44449e9d5eeab1635fe1b69f7f637788fd62c1e00
Tx public key: f3f2e5030a0fcd5e002eb62583deb98f3f5cf1eac8ccdf336b6776cedfcd609a
Timestamp: 1729512554 Timestamp [UCT]: 2024-10-21 12:09:14 Age [y:d:h:m:s]: 01:020:18:39:07
Block: 1136387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273235 RingCT/type: yes/0
Extra: 01f3f2e5030a0fcd5e002eb62583deb98f3f5cf1eac8ccdf336b6776cedfcd609a021100000001cab32bb9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b33324be67751ce9ff95cf2ef0feae7c798e4de8fefc981ac01f2faec31d9fc9 0.600000000000 1619732 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": 1136397, "vin": [ { "gen": { "height": 1136387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b33324be67751ce9ff95cf2ef0feae7c798e4de8fefc981ac01f2faec31d9fc9" } } ], "extra": [ 1, 243, 242, 229, 3, 10, 15, 205, 94, 0, 46, 182, 37, 131, 222, 185, 143, 63, 92, 241, 234, 200, 204, 223, 51, 107, 103, 118, 206, 223, 205, 96, 154, 2, 17, 0, 0, 0, 1, 202, 179, 43, 185, 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