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: e389af5df70546611d5baa09f06552bb96bbd491e8eac0fafaee2d54ef9d4011
Tx prefix hash: 36010421c138cbb587e07e0a5518e5f8a6d190fcbeb0aedc019506366bd155a3
Tx public key: 56eb608c2f0d3e7a4b5724ec51193eb0107edbc33fabd2ed06f290a1f7143526
| Timestamp: 1780817610 | Timestamp [UTC]: 2026-06-07 07:33:30 | Age [y:d:h:m:s]: 00:002:09:35:33 |
| Block: 7096 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1638 | RingCT/type: yes/0 |
| Extra: 0156eb608c2f0d3e7a4b5724ec51193eb0107edbc33fabd2ed06f290a1f7143526020900000004e49593ff00 | ||
1 output(s) for total of 34.711441464831 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe0fa72165b5e2cc00ca6051048bdf024f79d200cec552ba6e8483909e6ef07c | 34.711441464831 | 8748 of 0 | <77> |
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": 7156,
"vin": [ {
"gen": {
"height": 7096
}
}
],
"vout": [ {
"amount": 34711441464831,
"target": {
"tagged_key": {
"key": "fe0fa72165b5e2cc00ca6051048bdf024f79d200cec552ba6e8483909e6ef07c",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 86, 235, 96, 140, 47, 13, 62, 122, 75, 87, 36, 236, 81, 25, 62, 176, 16, 126, 219, 195, 63, 171, 210, 237, 6, 242, 144, 161, 247, 20, 53, 38, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}