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: 549308563d0e3463aac6e0d50cc1ae855a6d5dc3a7c32a9c37cfc351bd2136d4
Tx prefix hash: e87395a00057dd0003bcfbe38274c2e4519898d71f11848a73abcfb4cf190a57
Tx public key: 3730b0182e51480d4fd9e56b2c044328dcc79a6f8c6a894a130c280eff4ab672
| Timestamp: 1780401950 | Timestamp [UTC]: 2026-06-02 12:05:50 | Age [y:d:h:m:s]: 00:006:13:30:07 |
| Block: 5286 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2600 | RingCT/type: yes/0 |
| Extra: 013730b0182e51480d4fd9e56b2c044328dcc79a6f8c6a894a130c280eff4ab67202090000000326697be300 | ||
1 output(s) for total of 34.831483014831 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8046a8746aefc191a6688fabd184b5bfc67f12495b6b485d8064fa99ceaea967 | 34.831483014831 | 6703 of 0 | <12> |
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": 5346,
"vin": [ {
"gen": {
"height": 5286
}
}
],
"vout": [ {
"amount": 34831483014831,
"target": {
"tagged_key": {
"key": "8046a8746aefc191a6688fabd184b5bfc67f12495b6b485d8064fa99ceaea967",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 55, 48, 176, 24, 46, 81, 72, 13, 79, 217, 229, 107, 44, 4, 67, 40, 220, 199, 154, 111, 140, 106, 137, 74, 19, 12, 40, 14, 255, 74, 182, 114, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}