Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77bb0cd99f8b4631ef23c394bf8f884a0407b6c1d91e040958cfb3065f280ecd

Tx prefix hash: 4779bc3de559fd57d99027b266d0c24f1bbe45ca63b7a751ce6bbe654baa1e52
Tx public key: 62b0a5962ed1922ec4fe0b16ea55e6d0ec80f27ac7d75ce7f2545772a0fe6af9
Timestamp: 1707964910 Timestamp [UCT]: 2024-02-15 02:41:50 Age [y:d:h:m:s]: 00:334:09:32:21
Block: 957768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239395 RingCT/type: yes/0
Extra: 0162b0a5962ed1922ec4fe0b16ea55e6d0ec80f27ac7d75ce7f2545772a0fe6af902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 552aad805ebf3964e56c987cdb023ee3df6e15a0451245c9d4d7f248474667a4 0.600000000000 1417117 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": 957778, "vin": [ { "gen": { "height": 957768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552aad805ebf3964e56c987cdb023ee3df6e15a0451245c9d4d7f248474667a4" } } ], "extra": [ 1, 98, 176, 165, 150, 46, 209, 146, 46, 196, 254, 11, 22, 234, 85, 230, 208, 236, 128, 242, 122, 199, 215, 92, 231, 242, 84, 87, 114, 160, 254, 106, 249, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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