Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c488dcdf98473c9d7f21820e9094f00febcf0553a551d9ec87b04c6467e49c

Tx prefix hash: 58b3665ecf99db5cc01d0352620ff880599c62d374a23b82b4fea2dd8888527e
Tx public key: b64b8d21e9d8d0c14eee8e773f889459bc770768a8b22191cb05c7c3de348e84
Timestamp: 1723777330 Timestamp [UCT]: 2024-08-16 03:02:10 Age [y:d:h:m:s]: 00:234:01:28:44
Block: 1088876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167144 RingCT/type: yes/0
Extra: 01b64b8d21e9d8d0c14eee8e773f889459bc770768a8b22191cb05c7c3de348e84021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec6c201a0d751f60b1f5fa598c22cd756f56663b144d8521bc8c95906c038ba8 0.600000000000 1563495 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": 1088886, "vin": [ { "gen": { "height": 1088876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec6c201a0d751f60b1f5fa598c22cd756f56663b144d8521bc8c95906c038ba8" } } ], "extra": [ 1, 182, 75, 141, 33, 233, 216, 208, 193, 78, 238, 142, 119, 63, 136, 148, 89, 188, 119, 7, 104, 168, 178, 33, 145, 203, 5, 199, 195, 222, 52, 142, 132, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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