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: ec6ef41a4037ed3d6f6bd5ae546e9a2192cb46f5e0e8f1bfbe76b8ee5d402c29
Tx prefix hash: 0b647381294b41ee6d00f8119e456c2fa8500998245dc6459150cbf504fd9923
Tx public key: 4daecf6a1165a791730e166f083172e7e31bd7630519b2813c584a8d29196573
| Timestamp: 1780864795 | Timestamp [UTC]: 2026-06-07 20:39:55 | Age [y:d:h:m:s]: 00:001:02:38:58 |
| Block: 7648 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 238 | RingCT/type: yes/0 |
| Extra: 014daecf6a1165a791730e166f083172e7e31bd7630519b2813c584a8d29196573020900000001e49593ff00 | ||
1 output(s) for total of 34.679934097324 HMNY
| stealth address | amount | amount idx | tag |
| 00: 009da8bfe1516bc630bf4dd6ef9cfa4703a336eb26872a6d260f06aa5e36d044 | 34.679934097324 | 9456 of 0 | <26> |
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": 7708,
"vin": [ {
"gen": {
"height": 7648
}
}
],
"vout": [ {
"amount": 34679934097324,
"target": {
"tagged_key": {
"key": "009da8bfe1516bc630bf4dd6ef9cfa4703a336eb26872a6d260f06aa5e36d044",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 77, 174, 207, 106, 17, 101, 167, 145, 115, 14, 22, 111, 8, 49, 114, 231, 227, 27, 215, 99, 5, 25, 178, 129, 60, 88, 74, 141, 41, 25, 101, 115, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}