Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae4f69197d25ace694bf069fb57ff07ff45180001f7008de381862e7a7b3bced

Tx prefix hash: fbb55b08b2aca7c00134937d455a68653d2ca8512100b3842661333abf5060da
Tx public key: 01de010c867a11c929c2486a00c76e51e92a10b2b58c74f799d4c6ad392313d5
Timestamp: 1694604800 Timestamp [UCT]: 2023-09-13 11:33:20 Age [y:d:h:m:s]: 01:129:02:24:11
Block: 847200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353550 RingCT/type: yes/0
Extra: 0101de010c867a11c929c2486a00c76e51e92a10b2b58c74f799d4c6ad392313d5021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.956918104000 dcy

stealth address amount amount idx
00: 05555f051388ecde229a95863c67a37732c9201fa7f1b2ba7a1cd9d7b54f3be7 0.956918104000 1300704 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": 847210, "vin": [ { "gen": { "height": 847200 } } ], "vout": [ { "amount": 956918104, "target": { "key": "05555f051388ecde229a95863c67a37732c9201fa7f1b2ba7a1cd9d7b54f3be7" } } ], "extra": [ 1, 1, 222, 1, 12, 134, 122, 17, 201, 41, 194, 72, 106, 0, 199, 110, 81, 233, 42, 16, 178, 181, 140, 116, 247, 153, 212, 198, 173, 57, 35, 19, 213, 2, 17, 0, 0, 0, 4, 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