Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 203d1cb4fa300ac42fb47dacabc7f708286df4f5031fd0b0771e1857ecbff2cc

Tx prefix hash: 4c4bfe0e2c8fb2c9daf5c232bbe4b293964c48b37ecb4084746fce8ca2a39f84
Tx public key: d8d3719596646048a1ed60e931fbb7d8a36245cf25bcd58256007a23fc891fb6
Timestamp: 1721320079 Timestamp [UCT]: 2024-07-18 16:27:59 Age [y:d:h:m:s]: 00:262:09:20:22
Block: 1068522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187414 RingCT/type: yes/0
Extra: 01d8d3719596646048a1ed60e931fbb7d8a36245cf25bcd58256007a23fc891fb6021100000003ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 932802a0f7fd634ccaf68f4069e2d3a7da4bb7e13b195fc7bd5dbae3034b6e62 0.600000000000 1539601 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": 1068532, "vin": [ { "gen": { "height": 1068522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "932802a0f7fd634ccaf68f4069e2d3a7da4bb7e13b195fc7bd5dbae3034b6e62" } } ], "extra": [ 1, 216, 211, 113, 149, 150, 100, 96, 72, 161, 237, 96, 233, 49, 251, 183, 216, 163, 98, 69, 207, 37, 188, 213, 130, 86, 0, 122, 35, 252, 137, 31, 182, 2, 17, 0, 0, 0, 3, 221, 211, 219, 145, 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