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: 5690409b11162973b4be53a83548c5afcedba65401b280c6a76c6d53ca3c642f
Tx prefix hash: f3db1e9152c47e4188b19862825eb404af8e6c88c73ee06499e1533dc3725ccc
Tx public key: 2e2bf8577ef6f9d89810ec0f68cf58bb488665b5dce01a652511ee344f459387
| Timestamp: 1779896795 | Timestamp [UTC]: 2026-05-27 15:46:35 | Age [y:d:h:m:s]: 00:012:09:49:22 |
| Block: 3109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4777 | RingCT/type: yes/0 |
| Extra: 012e2bf8577ef6f9d89810ec0f68cf58bb488665b5dce01a652511ee344f45938702090000000226697be300 | ||
1 output(s) for total of 34.976414540592 HMNY
| stealth address | amount | amount idx | tag |
| 00: b1c6e1b394826470a6021e6f230e18c26036d10f394529f108832958ab22c9c9 | 34.976414540592 | 3709 of 0 | <7e> |
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": 3169,
"vin": [ {
"gen": {
"height": 3109
}
}
],
"vout": [ {
"amount": 34976414540592,
"target": {
"tagged_key": {
"key": "b1c6e1b394826470a6021e6f230e18c26036d10f394529f108832958ab22c9c9",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 46, 43, 248, 87, 126, 246, 249, 216, 152, 16, 236, 15, 104, 207, 88, 187, 72, 134, 101, 181, 220, 224, 26, 101, 37, 17, 238, 52, 79, 69, 147, 135, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}