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: b34248335d3fa15f81d56b55c3f21cc57b1daa341e67f1d9b04700f16d5333bd
Tx prefix hash: 8e809b42b21b37108af83afee721e849c6103c84705d00d19f2ba1f60b043ed0
Tx public key: 640531e93eb51f88a185d1afc4fcb0bb2720f81c43049b1e20d8547cc567f083
| Timestamp: 1780992352 | Timestamp [UTC]: 2026-06-09 08:05:52 | Age [y:d:h:m:s]: 00:000:09:14:11 |
| Block: 8260 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 484 | RingCT/type: yes/0 |
| Extra: 01640531e93eb51f88a185d1afc4fcb0bb2720f81c43049b1e20d8547cc567f083020900000003e49593ff00 | ||
1 output(s) for total of 34.634462137041 HMNY
| stealth address | amount | amount idx | tag |
| 00: cd7dad78bb4722724999b414404a8320b1e6c7a475626ce8b15110d417bee2f1 | 34.634462137041 | 10222 of 0 | <8e> |
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": 8320,
"vin": [ {
"gen": {
"height": 8260
}
}
],
"vout": [ {
"amount": 34634462137041,
"target": {
"tagged_key": {
"key": "cd7dad78bb4722724999b414404a8320b1e6c7a475626ce8b15110d417bee2f1",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 100, 5, 49, 233, 62, 181, 31, 136, 161, 133, 209, 175, 196, 252, 176, 187, 39, 32, 248, 28, 67, 4, 155, 30, 32, 216, 84, 124, 197, 103, 240, 131, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}