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: 69416598202e7492ec7886cfb628403ca404be84e0929bb7ec020a51e6a02518
Tx prefix hash: 75faf6c0b9d4aa4035a371b509203e8d6884b15e3c6a77dd6aa50432ca55233a
Tx public key: 67d2483f792be8ce1a51a9ac35660608dc4ab6b8e594b463f3ad6f2f7769e98d
| Timestamp: 1780846805 | Timestamp [UTC]: 2026-06-07 15:40:05 | Age [y:d:h:m:s]: 00:001:09:55:52 |
| Block: 7514 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 372 | RingCT/type: yes/0 |
| Extra: 0167d2483f792be8ce1a51a9ac35660608dc4ab6b8e594b463f3ad6f2f7769e98d020900000001e49593ff00 | ||
1 output(s) for total of 34.683778016621 HMNY
| stealth address | amount | amount idx | tag |
| 00: 47f2a2c2e432173e194783d455e611d335716fa33c9347eb0f4dbbb47c7253cd | 34.683778016621 | 9264 of 0 | <24> |
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": 7574,
"vin": [ {
"gen": {
"height": 7514
}
}
],
"vout": [ {
"amount": 34683778016621,
"target": {
"tagged_key": {
"key": "47f2a2c2e432173e194783d455e611d335716fa33c9347eb0f4dbbb47c7253cd",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 103, 210, 72, 63, 121, 43, 232, 206, 26, 81, 169, 172, 53, 102, 6, 8, 220, 74, 182, 184, 229, 148, 180, 99, 243, 173, 111, 47, 119, 105, 233, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}