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: ed22af2ee51be321dbdd34974557cca025f0cf2861d2f0ec46bf510d4f44c480
Tx prefix hash: 4cc52259af8e5ac4d21074689c47828dc38352a414d8148ad0ea533b1bd935c8
Tx public key: e2319a18ec5d05d32faa1aa67969df96bc715eb37bc22e21d9d18cd92c2fc2d5
| Timestamp: 1779468114 | Timestamp [UTC]: 2026-05-22 16:41:54 | Age [y:d:h:m:s]: 00:017:08:04:53 |
| Block: 537 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7349 | RingCT/type: yes/0 |
| Extra: 01e2319a18ec5d05d32faa1aa67969df96bc715eb37bc22e21d9d18cd92c2fc2d502090000000193369e7d00 | ||
1 output(s) for total of 35.148420084252 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5bb207cf7343a4e38002fe0beb6d19d66405af2510b66de2886672ca6d38037a | 35.148420084252 | 541 of 0 | <fd> |
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": 597,
"vin": [ {
"gen": {
"height": 537
}
}
],
"vout": [ {
"amount": 35148420084252,
"target": {
"tagged_key": {
"key": "5bb207cf7343a4e38002fe0beb6d19d66405af2510b66de2886672ca6d38037a",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 226, 49, 154, 24, 236, 93, 5, 211, 47, 170, 26, 166, 121, 105, 223, 150, 188, 113, 94, 179, 123, 194, 46, 33, 217, 209, 140, 217, 44, 47, 194, 213, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}