Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8815b96496081e143e051abbc368f94153dece7aa178ad7d0345b2adfde960e

Tx prefix hash: 2c4db437391d041c36f7274a08c6bdd75a864d3dc0044d969cbb6876ce1643d0
Tx public key: e2eff6fe27a68fd62b876924c9e6d8529a51a4b9a16e06e30c911d54083ed87a
Timestamp: 1720230358 Timestamp [UCT]: 2024-07-06 01:45:58 Age [y:d:h:m:s]: 00:321:04:45:23
Block: 1059461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229549 RingCT/type: yes/0
Extra: 01e2eff6fe27a68fd62b876924c9e6d8529a51a4b9a16e06e30c911d54083ed87a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f10f391cb7201753b51fabbabcb4b98737f3ff24357e0a1a8228dadb08b9000 0.600000000000 1529930 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": 1059471, "vin": [ { "gen": { "height": 1059461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f10f391cb7201753b51fabbabcb4b98737f3ff24357e0a1a8228dadb08b9000" } } ], "extra": [ 1, 226, 239, 246, 254, 39, 166, 143, 214, 43, 135, 105, 36, 201, 230, 216, 82, 154, 81, 164, 185, 161, 110, 6, 227, 12, 145, 29, 84, 8, 62, 216, 122, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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