Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c367f0888d0dca86a0a34dc0abdf5be1d1f0389237e973c217e0d99eebcb0a6

Tx prefix hash: f3e80599d0825ba63625943eaf005b0a1b3bd859159408bb8232cb4ce4b19766
Tx public key: 4a8deedd760d25ff1e32e295b82e13b19d25f0b6680a5c52ce8530c935ddb43c
Timestamp: 1728411346 Timestamp [UCT]: 2024-10-08 18:15:46 Age [y:d:h:m:s]: 00:173:12:47:23
Block: 1127295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123799 RingCT/type: yes/0
Extra: 014a8deedd760d25ff1e32e295b82e13b19d25f0b6680a5c52ce8530c935ddb43c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a868558a758a6818ee02dcd8d74b6d6e2f3483154916d41bfab37ca5342786 0.600000000000 1610096 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": 1127305, "vin": [ { "gen": { "height": 1127295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a868558a758a6818ee02dcd8d74b6d6e2f3483154916d41bfab37ca5342786" } } ], "extra": [ 1, 74, 141, 238, 221, 118, 13, 37, 255, 30, 50, 226, 149, 184, 46, 19, 177, 157, 37, 240, 182, 104, 10, 92, 82, 206, 133, 48, 201, 53, 221, 180, 60, 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