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: 07e643f9f47b36dd392421ddd559d0703a37d5b54ffa3b1aa148d62b27e0a29f
Tx prefix hash: 0d6eaa7307f9fca6a2c77fc618cb27906a62bf2eac0230e84e624b9c68bb62a2
Tx public key: 36915777fbbb8e0224e11330aabb2d286d916949c0176d8b94aaac79cb56b5a8
| Timestamp: 1780063712 | Timestamp [UTC]: 2026-05-29 14:08:32 | Age [y:d:h:m:s]: 00:010:09:10:21 |
| Block: 4554 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3332 | RingCT/type: yes/0 |
| Extra: 0136915777fbbb8e0224e11330aabb2d286d916949c0176d8b94aaac79cb56b5a802090000000526697be300 | ||
1 output(s) for total of 34.884264017932 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1d078b3b38383f199d3b37598f14909e8c15999d034fb0bf1720f5c1e88f4d4 | 34.884264017932 | 5715 of 0 | <15> |
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": 4614,
"vin": [ {
"gen": {
"height": 4554
}
}
],
"vout": [ {
"amount": 34884264017932,
"target": {
"tagged_key": {
"key": "c1d078b3b38383f199d3b37598f14909e8c15999d034fb0bf1720f5c1e88f4d4",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 54, 145, 87, 119, 251, 187, 142, 2, 36, 225, 19, 48, 170, 187, 45, 40, 109, 145, 105, 73, 192, 23, 109, 139, 148, 170, 172, 121, 203, 86, 181, 168, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}