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: 08cbd71c31bd23adb83b8b7d6a9e57591b32311aefaf3194c3f0aa091f8fbbd2
Tx prefix hash: ce9f2dfec2af5fa7d29290808be6f2425bfbd08d01608cc4e9098b383f29a6fa
Tx public key: d04421c04a83b3bc9c06028061c41e12519a04662f2dd2ae8dd1b47d7f9effe3
| Timestamp: 1780756665 | Timestamp [UTC]: 2026-06-06 14:37:45 | Age [y:d:h:m:s]: 00:010:17:51:27 |
| Block: 6539 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2206 | RingCT/type: yes/0 |
| Extra: 01d04421c04a83b3bc9c06028061c41e12519a04662f2dd2ae8dd1b47d7f9effe3020900000001e49593ff00 | ||
1 output(s) for total of 34.748338294993 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ed2367477725fe2a8e07c13a14d3870dd4b3230455df6ffbd98cfe7fee8e84e | 34.748338294993 | 8045 of 0 | <e0> |
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": 6599,
"vin": [ {
"gen": {
"height": 6539
}
}
],
"vout": [ {
"amount": 34748338294993,
"target": {
"tagged_key": {
"key": "7ed2367477725fe2a8e07c13a14d3870dd4b3230455df6ffbd98cfe7fee8e84e",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 208, 68, 33, 192, 74, 131, 179, 188, 156, 6, 2, 128, 97, 196, 30, 18, 81, 154, 4, 102, 47, 45, 210, 174, 141, 209, 180, 125, 127, 158, 255, 227, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}