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: c916fe4501949c84b2144d2294c04ecae43c8bf5ff314a6e3a0d6091193ac586
Tx prefix hash: e9377350ff29201cd2065723796e37d4c345d926abb85c3b60bb953faa6ff3b1
Tx public key: e6473633a0f11d856eafb0b93b7fb0a219c9e5f9c99215ae103f7482bea4d108
| Timestamp: 1779782743 | Timestamp [UTC]: 2026-05-26 08:05:43 | Age [y:d:h:m:s]: 00:013:17:30:14 |
| Block: 2130 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5756 | RingCT/type: yes/0 |
| Extra: 01e6473633a0f11d856eafb0b93b7fb0a219c9e5f9c99215ae103f7482bea4d10802090000000226697be300 | ||
1 output(s) for total of 35.041786878548 HMNY
| stealth address | amount | amount idx | tag |
| 00: a89e5b2a9f933d7106a4328a08b4f63101ae9c5b397bc1f6db8dcba11b1227cc | 35.041786878548 | 2454 of 0 | <aa> |
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": 2190,
"vin": [ {
"gen": {
"height": 2130
}
}
],
"vout": [ {
"amount": 35041786878548,
"target": {
"tagged_key": {
"key": "a89e5b2a9f933d7106a4328a08b4f63101ae9c5b397bc1f6db8dcba11b1227cc",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 230, 71, 54, 51, 160, 241, 29, 133, 110, 175, 176, 185, 59, 127, 176, 162, 25, 201, 229, 249, 201, 146, 21, 174, 16, 63, 116, 130, 190, 164, 209, 8, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}