Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e534bba330f01c1fc38461e3bc920d7d4f71ea2af8e2eaf8891aab0f2bc210

Tx prefix hash: 69b460309f67a8ca8413c344fd74bff708ffd664847f12badfe6de6e022571d5
Tx public key: 7f4148c4b5f0573bb456e5682ed8a4995aa12909696b6e01c5440ee9cdc1ed08
Timestamp: 1735452766 Timestamp [UCT]: 2024-12-29 06:12:46 Age [y:d:h:m:s]: 00:314:18:45:54
Block: 1185532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222486 RingCT/type: yes/0
Extra: 017f4148c4b5f0573bb456e5682ed8a4995aa12909696b6e01c5440ee9cdc1ed08021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4ab94c6df6370594d26b168b3fce5e5cb44ae4c4c478052bc462e8b01f8a751 0.600000000000 1672005 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": 1185542, "vin": [ { "gen": { "height": 1185532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4ab94c6df6370594d26b168b3fce5e5cb44ae4c4c478052bc462e8b01f8a751" } } ], "extra": [ 1, 127, 65, 72, 196, 181, 240, 87, 59, 180, 86, 229, 104, 46, 216, 164, 153, 90, 161, 41, 9, 105, 107, 110, 1, 197, 68, 14, 233, 205, 193, 237, 8, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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