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: f269fd9944109459c99ec26f8733cd16ea6cd62dbd1074950792544e157df50b
Tx prefix hash: aa06ada4029f88d9bf2619fc52ba8c938a3ac2fb750af741f680019c6c09532e
Tx public key: 7950fa5cedcc1d520ec103f1f03e3808594857f75346ce322df7bbca0f4aa7b9
| Timestamp: 1780847496 | Timestamp [UTC]: 2026-06-07 15:51:36 | Age [y:d:h:m:s]: 00:007:16:27:59 |
| Block: 7521 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1224 | RingCT/type: yes/0 |
| Extra: 017950fa5cedcc1d520ec103f1f03e3808594857f75346ce322df7bbca0f4aa7b9020900000002e49593ff00 | ||
1 output(s) for total of 34.683314940874 HMNY
| stealth address | amount | amount idx | tag |
| 00: 821d632f0b0f2dc7bdc33c24d83bda77bccd0c78f63d652624700a2c7cbdd991 | 34.683314940874 | 9273 of 0 | <fe> |
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": 7581,
"vin": [ {
"gen": {
"height": 7521
}
}
],
"vout": [ {
"amount": 34683314940874,
"target": {
"tagged_key": {
"key": "821d632f0b0f2dc7bdc33c24d83bda77bccd0c78f63d652624700a2c7cbdd991",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 121, 80, 250, 92, 237, 204, 29, 82, 14, 193, 3, 241, 240, 62, 56, 8, 89, 72, 87, 247, 83, 70, 206, 50, 45, 247, 187, 202, 15, 74, 167, 185, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}