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: 93057078ff26e857d72983f901846fef844921189d39d2cc41438c33bd20dc99
Tx prefix hash: efb1f5b5e0d552cf79e18ffe8c94e1f18e72dc10a2961dc86713d1df0b9a828d
Tx public key: fe7a3a563453dac1d5967fb56c9ea62850f9befdc41b4cb545b67d4ad909c89a
| Timestamp: 1780845760 | Timestamp [UTC]: 2026-06-07 15:22:40 | Age [y:d:h:m:s]: 00:001:05:49:27 |
| Block: 7504 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 382 | RingCT/type: yes/0 |
| Extra: 01fe7a3a563453dac1d5967fb56c9ea62850f9befdc41b4cb545b67d4ad909c89a020900000003e49593ff00 | ||
1 output(s) for total of 34.684439564126 HMNY
| stealth address | amount | amount idx | tag |
| 00: 417a09d99d182e31618365ce55c536c2eb772b417d15da46990ed5f8092e1a81 | 34.684439564126 | 9250 of 0 | <c7> |
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": 7564,
"vin": [ {
"gen": {
"height": 7504
}
}
],
"vout": [ {
"amount": 34684439564126,
"target": {
"tagged_key": {
"key": "417a09d99d182e31618365ce55c536c2eb772b417d15da46990ed5f8092e1a81",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 254, 122, 58, 86, 52, 83, 218, 193, 213, 150, 127, 181, 108, 158, 166, 40, 80, 249, 190, 253, 196, 27, 76, 181, 69, 182, 125, 74, 217, 9, 200, 154, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}