Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8cd022afc670524bbc2845cd056ce1501a6232638466af52921b8930956478

Tx prefix hash: 14597f8e211f6b1eb42a7a4a2ca89674701517b26c27698d4be8dea3c0fcc8c0
Tx public key: 0e14cfa878d83988f0633dbe15ed3e72a21cbbb03cf8b3230ca933eb1ed36e0a
Timestamp: 1723849364 Timestamp [UCT]: 2024-08-16 23:02:44 Age [y:d:h:m:s]: 01:112:02:40:21
Block: 1089471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338613 RingCT/type: yes/0
Extra: 010e14cfa878d83988f0633dbe15ed3e72a21cbbb03cf8b3230ca933eb1ed36e0a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f732afb9d88a5ec791fd86937a64fe1c6a294bcdc13eb403fe9db22b809475c6 0.600000000000 1564092 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": 1089481, "vin": [ { "gen": { "height": 1089471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f732afb9d88a5ec791fd86937a64fe1c6a294bcdc13eb403fe9db22b809475c6" } } ], "extra": [ 1, 14, 20, 207, 168, 120, 216, 57, 136, 240, 99, 61, 190, 21, 237, 62, 114, 162, 28, 187, 176, 60, 248, 179, 35, 12, 169, 51, 235, 30, 211, 110, 10, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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