Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89789e21e289008b16fc942a33a50e2b3bada42e4d4be60c7325974fd7432624

Tx prefix hash: b86a65eaae427cfcdc99efb1bb67cca1ea822955bddc0234581446270ced7826
Tx public key: e8551436f9cb68dbecf8a89b2f73ee31a1a11fdea626e25a0526f0544c97ab27
Timestamp: 1719222662 Timestamp [UCT]: 2024-06-24 09:51:02 Age [y:d:h:m:s]: 00:334:12:39:30
Block: 1051104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239092 RingCT/type: yes/0
Extra: 01e8551436f9cb68dbecf8a89b2f73ee31a1a11fdea626e25a0526f0544c97ab270211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 838448b03849b9dd7594e071c7bf5243f9fb3e3a2bfae364902c121adfbfa1b3 0.600000000000 1521339 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": 1051114, "vin": [ { "gen": { "height": 1051104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "838448b03849b9dd7594e071c7bf5243f9fb3e3a2bfae364902c121adfbfa1b3" } } ], "extra": [ 1, 232, 85, 20, 54, 249, 203, 104, 219, 236, 248, 168, 155, 47, 115, 238, 49, 161, 161, 31, 222, 166, 38, 226, 90, 5, 38, 240, 84, 76, 151, 171, 39, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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