Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8a0e8994959dce64e4701636dc4fcf2be6a79ba2350fccb934a9e11dbe98177

Tx prefix hash: 54943a7142558ebb8fed79eb39c1fce0add75e5ccdf65bd94dbae02a22913baf
Tx public key: 16939a26c5ffcdcf1ed66c013751ef15e63569b52c4f97dfa5c1ba9b231dfb0e
Timestamp: 1720807434 Timestamp [UCT]: 2024-07-12 18:03:54 Age [y:d:h:m:s]: 00:319:03:50:44
Block: 1064258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228065 RingCT/type: yes/0
Extra: 0116939a26c5ffcdcf1ed66c013751ef15e63569b52c4f97dfa5c1ba9b231dfb0e02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02fa71f590f427f790707cd1d467079dd76e354db2d9e3ff35ae3248b223a2e9 0.600000000000 1534781 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": 1064268, "vin": [ { "gen": { "height": 1064258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02fa71f590f427f790707cd1d467079dd76e354db2d9e3ff35ae3248b223a2e9" } } ], "extra": [ 1, 22, 147, 154, 38, 197, 255, 205, 207, 30, 214, 108, 1, 55, 81, 239, 21, 230, 53, 105, 181, 44, 79, 151, 223, 165, 193, 186, 155, 35, 29, 251, 14, 2, 17, 0, 0, 0, 12, 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