Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d4dcc658ff5dc42c4e237578cc33469ffd2a48fce0ae1196cc48e444322be85

Tx prefix hash: 89b606398be9826fd9059fe230b6bcb4f217c50038eeda5cd12393b4b3ce47a8
Tx public key: d652e8efb03c746e18ed00783e7a966e76c62b594c678bc3aa6ad1a5be7002b8
Timestamp: 1696173706 Timestamp [UCT]: 2023-10-01 15:21:46 Age [y:d:h:m:s]: 01:025:01:03:26
Block: 860225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279148 RingCT/type: yes/0
Extra: 01d652e8efb03c746e18ed00783e7a966e76c62b594c678bc3aa6ad1a5be7002b802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.866398158000 dcy

stealth address amount amount idx
00: 52c21e17bcf29bf1937e51ef9c35e10de9926b431668b75c226e3050d851e319 0.866398158000 1314497 of 0

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": 860235, "vin": [ { "gen": { "height": 860225 } } ], "vout": [ { "amount": 866398158, "target": { "key": "52c21e17bcf29bf1937e51ef9c35e10de9926b431668b75c226e3050d851e319" } } ], "extra": [ 1, 214, 82, 232, 239, 176, 60, 116, 110, 24, 237, 0, 120, 62, 122, 150, 110, 118, 198, 43, 89, 76, 103, 139, 195, 170, 106, 209, 165, 190, 112, 2, 184, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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