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: 8756a482803fccbf52a310d87366b0b12b0656c22a7edbc7fadd80e99a6873e3
Tx prefix hash: 4f00fef299911fbb101fab28d6228031efe8627f44b800db85cb8df71a6be1c9
Tx public key: 385eb4eb48678e58c924ebe8586c3d57e1abf0c2e8f6d38c58791d5f7a8edfa6
| Timestamp: 1780799747 | Timestamp [UTC]: 2026-06-07 02:35:47 | Age [y:d:h:m:s]: 00:001:22:11:00 |
| Block: 6819 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1067 | RingCT/type: yes/0 |
| Extra: 01385eb4eb48678e58c924ebe8586c3d57e1abf0c2e8f6d38c58791d5f7a8edfa6020900000002e49593ff00 | ||
1 output(s) for total of 34.729785617089 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe1d6d99c8fcbe17849eb1a7cc0bdfea9fa2f80fefca6a2ed8db5dd6b282ad81 | 34.729785617089 | 8419 of 0 | <d4> |
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": 6879,
"vin": [ {
"gen": {
"height": 6819
}
}
],
"vout": [ {
"amount": 34729785617089,
"target": {
"tagged_key": {
"key": "fe1d6d99c8fcbe17849eb1a7cc0bdfea9fa2f80fefca6a2ed8db5dd6b282ad81",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 56, 94, 180, 235, 72, 103, 142, 88, 201, 36, 235, 232, 88, 108, 61, 87, 225, 171, 240, 194, 232, 246, 211, 140, 88, 121, 29, 95, 122, 142, 223, 166, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}