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: 14537bfa2205db3b9cbf801eeb8c0b3e39da5473bcb6f0ca5f0c1ffc50d88abf
Tx prefix hash: 1ca6e040bc8ad282595f13c571208ca46f5936d2ff44337cbcee997eb1cdb05c
Tx public key: d4f075bf7322a24ac8bd03e156071a6bc26d4f36dabbeeda05733dbc079af26b
| Timestamp: 1780834500 | Timestamp [UTC]: 2026-06-07 12:15:00 | Age [y:d:h:m:s]: 00:001:13:20:57 |
| Block: 7385 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 501 | RingCT/type: yes/0 |
| Extra: 01d4f075bf7322a24ac8bd03e156071a6bc26d4f36dabbeeda05733dbc079af26b020900000001e49593ff00 | ||
1 output(s) for total of 34.692312948017 HMNY
| stealth address | amount | amount idx | tag |
| 00: d20734e6b53c284b226673710ed494dfe0c2c0402dd937913e69432d112345e9 | 34.692312948017 | 9093 of 0 | <c5> |
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": 7445,
"vin": [ {
"gen": {
"height": 7385
}
}
],
"vout": [ {
"amount": 34692312948017,
"target": {
"tagged_key": {
"key": "d20734e6b53c284b226673710ed494dfe0c2c0402dd937913e69432d112345e9",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 212, 240, 117, 191, 115, 34, 162, 74, 200, 189, 3, 225, 86, 7, 26, 107, 194, 109, 79, 54, 218, 187, 238, 218, 5, 115, 61, 188, 7, 154, 242, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}