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: 90b822b5a1a44c5b419a4cb0f7d87fe8ecf899683fd02166546ebb9994806902
Tx prefix hash: 1c2e939f6e42bf6b8a6ed29221ca404327fc583b6b9092f051f69a848c13446f
Tx public key: 2eb8dfd66dd8c7c83c51fa8ccfd5c3d36304cf2d9dee6f802071d97c0689178d
| Timestamp: 1780839004 | Timestamp [UTC]: 2026-06-07 13:30:04 | Age [y:d:h:m:s]: 00:001:09:48:49 |
| Block: 7446 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 440 | RingCT/type: yes/0 |
| Extra: 012eb8dfd66dd8c7c83c51fa8ccfd5c3d36304cf2d9dee6f802071d97c0689178d020900000004e49593ff00 | ||
1 output(s) for total of 34.688276788497 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5b74240ce8aa6bc3a62b5acaf8dc145055a4feb60bdfedfb3798a03b426b4120 | 34.688276788497 | 9170 of 0 | <fd> |
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": 7506,
"vin": [ {
"gen": {
"height": 7446
}
}
],
"vout": [ {
"amount": 34688276788497,
"target": {
"tagged_key": {
"key": "5b74240ce8aa6bc3a62b5acaf8dc145055a4feb60bdfedfb3798a03b426b4120",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 46, 184, 223, 214, 109, 216, 199, 200, 60, 81, 250, 140, 207, 213, 195, 211, 99, 4, 207, 45, 157, 238, 111, 128, 32, 113, 217, 124, 6, 137, 23, 141, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}