Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b635c9c062836818b2dfcaf8566c80c73ef554a1c716da4b9d1041622211a370

Tx prefix hash: 065780c925baf788da953206aa50292dd464ed04b179cfe91044654e6a60c026
Tx public key: 1ea3f71d244324f90c5e6d3b47b5656b89b7de5a3eb3ecec78c8088b126385d7
Timestamp: 1720789562 Timestamp [UCT]: 2024-07-12 13:06:02 Age [y:d:h:m:s]: 00:246:01:49:21
Block: 1064111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175805 RingCT/type: yes/0
Extra: 011ea3f71d244324f90c5e6d3b47b5656b89b7de5a3eb3ecec78c8088b126385d702110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02ab3ce3ea336044f2e0cdf5e6ac595a796a918081bf214c0e30a26137d978c 0.600000000000 1534634 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": 1064121, "vin": [ { "gen": { "height": 1064111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02ab3ce3ea336044f2e0cdf5e6ac595a796a918081bf214c0e30a26137d978c" } } ], "extra": [ 1, 30, 163, 247, 29, 36, 67, 36, 249, 12, 94, 109, 59, 71, 181, 101, 107, 137, 183, 222, 90, 62, 179, 236, 236, 120, 200, 8, 139, 18, 99, 133, 215, 2, 17, 0, 0, 0, 9, 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