Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfad42e22d5acf545f214fd9c4ff4ca34c1c4d958b97516b30064b976d86b841

Tx prefix hash: e4ccf4c66303c6cbbc627adc9697e8e8cc58a77cc25125780f4a07fd74067cb1
Tx public key: ea1122399b0423fd837773b8000764e3ce28e83f875fa3a6614167c7850b4f94
Timestamp: 1722730777 Timestamp [UCT]: 2024-08-04 00:19:37 Age [y:d:h:m:s]: 01:097:06:23:06
Block: 1080193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328000 RingCT/type: yes/0
Extra: 01ea1122399b0423fd837773b8000764e3ce28e83f875fa3a6614167c7850b4f94021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20179af8d273db7812d451cbd9f41d3c91985e716965dc7b2f93022c4391413 0.600000000000 1553462 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": 1080203, "vin": [ { "gen": { "height": 1080193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20179af8d273db7812d451cbd9f41d3c91985e716965dc7b2f93022c4391413" } } ], "extra": [ 1, 234, 17, 34, 57, 155, 4, 35, 253, 131, 119, 115, 184, 0, 7, 100, 227, 206, 40, 232, 63, 135, 95, 163, 166, 97, 65, 103, 199, 133, 11, 79, 148, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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