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: 1ea8756354e1730aa94e717aaa53a01b130332bf5938a5f52080248b8b37b08f
Tx prefix hash: d2cd3e2a58b7e28485063f64948c0d8306194fd46c1053efb646de02b42442a1
Tx public key: 32f8c89d3db6cbdd3bdc40cdaf08faab23041cd124e1d22094709069ad64f96d
| Timestamp: 1779996993 | Timestamp [UTC]: 2026-05-28 19:36:33 | Age [y:d:h:m:s]: 00:011:05:59:24 |
| Block: 4034 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3852 | RingCT/type: yes/0 |
| Extra: 0132f8c89d3db6cbdd3bdc40cdaf08faab23041cd124e1d22094709069ad64f96d02090000000426697be300 | ||
1 output(s) for total of 34.914760085966 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6b8a47dd16b9a3a5b4e177b6bc3338281626d26b7a21e93931061bf9cf1e77eb | 34.914760085966 | 4993 of 0 | <b5> |
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": 4094,
"vin": [ {
"gen": {
"height": 4034
}
}
],
"vout": [ {
"amount": 34914760085966,
"target": {
"tagged_key": {
"key": "6b8a47dd16b9a3a5b4e177b6bc3338281626d26b7a21e93931061bf9cf1e77eb",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 50, 248, 200, 157, 61, 182, 203, 221, 59, 220, 64, 205, 175, 8, 250, 171, 35, 4, 28, 209, 36, 225, 210, 32, 148, 112, 144, 105, 173, 100, 249, 109, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}