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: ad60b6ef440f394e1b165645f4efd0dfa0ac618f924136db3e2b38cf04fc4cb9
Tx prefix hash: b7429822ccc32d8e37960b8d6df265d6f364376f5fd378967d13a1ae5716887a
Tx public key: 29007e09b8a61d5afbee70e9961f6e89f84ce2bf34c1a77abd76c5b57f21a662
| Timestamp: 1780701472 | Timestamp [UTC]: 2026-06-05 23:17:52 | Age [y:d:h:m:s]: 00:003:00:01:01 |
| Block: 6058 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1828 | RingCT/type: yes/0 |
| Extra: 0129007e09b8a61d5afbee70e9961f6e89f84ce2bf34c1a77abd76c5b57f21a662020900000001e49593ff00 | ||
1 output(s) for total of 34.780232284553 HMNY
| stealth address | amount | amount idx | tag |
| 00: be6e99f802c7a161832f5fca895f5aa600f1c89c2c8fc1905b157fe4659a49e8 | 34.780232284553 | 7527 of 0 | <e9> |
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": 6118,
"vin": [ {
"gen": {
"height": 6058
}
}
],
"vout": [ {
"amount": 34780232284553,
"target": {
"tagged_key": {
"key": "be6e99f802c7a161832f5fca895f5aa600f1c89c2c8fc1905b157fe4659a49e8",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 41, 0, 126, 9, 184, 166, 29, 90, 251, 238, 112, 233, 150, 31, 110, 137, 248, 76, 226, 191, 52, 193, 167, 122, 189, 118, 197, 181, 127, 33, 166, 98, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}