Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d819184f43fb35fe92cf40ac3e28cc1cb381b4f4fc7d4873fb4ee3bfd0108f

Tx prefix hash: b1b7a765a1740270ec645a177d2e2ec756f7762f8a813f412e0a8e972c9d64f6
Tx public key: d111e2c2a24184f705065dd77b50e55ef77affd1ba23a0baa061521f8fb1b4b9
Timestamp: 1699605944 Timestamp [UCT]: 2023-11-10 08:45:44 Age [y:d:h:m:s]: 01:213:13:55:41
Block: 888484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413874 RingCT/type: yes/0
Extra: 01d111e2c2a24184f705065dd77b50e55ef77affd1ba23a0baa061521f8fb1b4b9021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.698366954000 dcy

stealth address amount amount idx
00: d924aa81517a8ce02f46c696164f7f718220a1714b047d06aca87bcd448b1455 0.698366954000 1344427 of 0

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": 888494, "vin": [ { "gen": { "height": 888484 } } ], "vout": [ { "amount": 698366954, "target": { "key": "d924aa81517a8ce02f46c696164f7f718220a1714b047d06aca87bcd448b1455" } } ], "extra": [ 1, 209, 17, 226, 194, 162, 65, 132, 247, 5, 6, 93, 215, 123, 80, 229, 94, 247, 122, 255, 209, 186, 35, 160, 186, 160, 97, 82, 31, 143, 177, 180, 185, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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