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: 91b77fc924ac0061ddc21b91327d35ac013999ef7aad1b24aaf4bc74002346ba
Tx prefix hash: 76b2e254b7c017a810f16bcf317cfdf1e86ea5d4563f36f2f75391eca693cdcb
Tx public key: be331834d014d68a2925b867ebcc5e971a009a83474dc3b1c87955e84bb5acc3
| Timestamp: 1780693757 | Timestamp [UTC]: 2026-06-05 21:09:17 | Age [y:d:h:m:s]: 00:003:04:26:40 |
| Block: 5894 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1992 | RingCT/type: yes/0 |
| Extra: 01be331834d014d68a2925b867ebcc5e971a009a83474dc3b1c87955e84bb5acc3020900000001e49593ff00 | ||
1 output(s) for total of 34.791113433355 HMNY
| stealth address | amount | amount idx | tag |
| 00: 137fd606ac762b6bf0153e92b3e6dab886526f949fa7d37d1379b9bc777102d8 | 34.791113433355 | 7353 of 0 | <36> |
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": 5954,
"vin": [ {
"gen": {
"height": 5894
}
}
],
"vout": [ {
"amount": 34791113433355,
"target": {
"tagged_key": {
"key": "137fd606ac762b6bf0153e92b3e6dab886526f949fa7d37d1379b9bc777102d8",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 190, 51, 24, 52, 208, 20, 214, 138, 41, 37, 184, 103, 235, 204, 94, 151, 26, 0, 154, 131, 71, 77, 195, 177, 200, 121, 85, 232, 75, 181, 172, 195, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}