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: 7cc15fe012bcb812ad5df66f55db7cf8d7d07c2c59715dd1de5ffcb95d145367
Tx prefix hash: e53d4404ef4e487812b9d89c2b3f03c66ad644d589a5232fcbe9fc1f9d194450
Tx public key: af4423f42f8529f578cbd17cbc604238575c3518ebc8ca3b66a8250c248512b6
| Timestamp: 1779469121 | Timestamp [UTC]: 2026-05-22 16:58:41 | Age [y:d:h:m:s]: 00:025:15:37:33 |
| Block: 544 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8201 | RingCT/type: yes/0 |
| Extra: 01af4423f42f8529f578cbd17cbc604238575c3518ebc8ca3b66a8250c248512b602090000000593369e7d00 | ||
1 output(s) for total of 35.147950804900 HMNY
| stealth address | amount | amount idx | tag |
| 00: f3ff47de606b9c01768cc4014a7dffeb947a2343e4b8a7f38af06ed489fab798 | 35.147950804900 | 548 of 0 | <e5> |
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": 604,
"vin": [ {
"gen": {
"height": 544
}
}
],
"vout": [ {
"amount": 35147950804900,
"target": {
"tagged_key": {
"key": "f3ff47de606b9c01768cc4014a7dffeb947a2343e4b8a7f38af06ed489fab798",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 175, 68, 35, 244, 47, 133, 41, 245, 120, 203, 209, 124, 188, 96, 66, 56, 87, 92, 53, 24, 235, 200, 202, 59, 102, 168, 37, 12, 36, 133, 18, 182, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}