For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 80961343059eb478d366e42ca2f5f968eaf279f7817e4343b442cbdd72c8d44e
Tx prefix hash: b2fdaff839d7241ceeb330bb0da2ba8104760d93bd3a3493f14bda78eba21223
Tx public key: c766a662a9bc98237de1e0fb35fdac8e47cb794176deb9b6ef864e43e4943435
| Timestamp: 1779471247 | Timestamp [UTC]: 2026-05-22 17:34:07 | Age [y:d:h:m:s]: 00:017:08:01:50 |
| Block: 567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7319 | RingCT/type: yes/0 |
| Extra: 01c766a662a9bc98237de1e0fb35fdac8e47cb794176deb9b6ef864e43e494343502090000000493369e7d00 | ||
1 output(s) for total of 35.156926931144 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16c42833886614c6d103496bf41f1e0c21e624ff1a0e24872ee8fc6c1978719a | 35.156926931144 | 575 of 0 | <7a> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 627,
"vin": [ {
"gen": {
"height": 567
}
}
],
"vout": [ {
"amount": 35156926931144,
"target": {
"tagged_key": {
"key": "16c42833886614c6d103496bf41f1e0c21e624ff1a0e24872ee8fc6c1978719a",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 199, 102, 166, 98, 169, 188, 152, 35, 125, 225, 224, 251, 53, 253, 172, 142, 71, 203, 121, 65, 118, 222, 185, 182, 239, 134, 78, 67, 228, 148, 52, 53, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}