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: 3215c8fc305aea2a231b761f8fa0785ee983a75e6e250f1a6b9498f875885e9d
Tx prefix hash: 1e3c5a449e3b0194d617f2871e5b43f333aa42e6aff7e4ef85b818524901ba2e
Tx public key: bcecc0b55b5c90dddd3eff575c65f353cf5792b14aab35f7a6bd34b9ae9f045d
| Timestamp: 1780059238 | Timestamp [UTC]: 2026-05-29 12:53:58 | Age [y:d:h:m:s]: 00:016:19:25:37 |
| Block: 4495 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4250 | RingCT/type: yes/0 |
| Extra: 01bcecc0b55b5c90dddd3eff575c65f353cf5792b14aab35f7a6bd34b9ae9f045d02090000000526697be300 | ||
1 output(s) for total of 34.884073430097 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec532841444d77992fba3bf9f7beb1089c19037fad9ac8b91434b1a084f92042 | 34.884073430097 | 5634 of 0 | <f2> |
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": 4555,
"vin": [ {
"gen": {
"height": 4495
}
}
],
"vout": [ {
"amount": 34884073430097,
"target": {
"tagged_key": {
"key": "ec532841444d77992fba3bf9f7beb1089c19037fad9ac8b91434b1a084f92042",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 188, 236, 192, 181, 91, 92, 144, 221, 221, 62, 255, 87, 92, 101, 243, 83, 207, 87, 146, 177, 74, 171, 53, 247, 166, 189, 52, 185, 174, 159, 4, 93, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}