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: 90a08ba97a387de283b4ceebb200f1ee4f3b67ee0a7af0da380357e2884b6f25
Tx prefix hash: 3cd066c0822c02c052f27c328e8fa8911900e9681020cb08873abd939e9ec640
Tx public key: 2b59cb2c15de9ff4ee00daa96fd9c6903b1b61726cd4831b6cd77cd0201647c0
| Timestamp: 1780828787 | Timestamp [UTC]: 2026-06-07 10:39:47 | Age [y:d:h:m:s]: 00:001:10:32:20 |
| Block: 7307 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 579 | RingCT/type: yes/0 |
| Extra: 012b59cb2c15de9ff4ee00daa96fd9c6903b1b61726cd4831b6cd77cd0201647c0020900000001e49593ff00 | ||
1 output(s) for total of 34.697474623072 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4987d492e56587899b7ffbe523947f3985278b4255ccf3f5428f19c60d2b3d5b | 34.697474623072 | 8997 of 0 | <2b> |
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": 7367,
"vin": [ {
"gen": {
"height": 7307
}
}
],
"vout": [ {
"amount": 34697474623072,
"target": {
"tagged_key": {
"key": "4987d492e56587899b7ffbe523947f3985278b4255ccf3f5428f19c60d2b3d5b",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 43, 89, 203, 44, 21, 222, 159, 244, 238, 0, 218, 169, 111, 217, 198, 144, 59, 27, 97, 114, 108, 212, 131, 27, 108, 215, 124, 208, 32, 22, 71, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}