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: 4c420fb10fb5becbfd00a3aba86a37a1b9b0b0461d6d21e96b150b4a1fa3ccea
Tx prefix hash: f1f22591cccdebf43819c228abce42a6cdd03a2ec51de0f31b81560c66a90b58
Tx public key: e0aeb6e70bec1c4133f1a635d636080d5f1f3d74b2e116aa2e80b968031f8ab2
| Timestamp: 1779630819 | Timestamp [UTC]: 2026-05-24 13:53:39 | Age [y:d:h:m:s]: 00:015:14:39:23 |
| Block: 887 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7126 | RingCT/type: yes/0 |
| Extra: 01e0aeb6e70bec1c4133f1a635d636080d5f1f3d74b2e116aa2e80b968031f8ab2020900000001ba6d17be00 | ||
1 output(s) for total of 35.124963790288 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64b68790866f2f954c8dc36fefe78ce5bd9272b336e87afd9a4f1b870931b8b6 | 35.124963790288 | 1019 of 0 | <d3> |
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": 947,
"vin": [ {
"gen": {
"height": 887
}
}
],
"vout": [ {
"amount": 35124963790288,
"target": {
"tagged_key": {
"key": "64b68790866f2f954c8dc36fefe78ce5bd9272b336e87afd9a4f1b870931b8b6",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 224, 174, 182, 231, 11, 236, 28, 65, 51, 241, 166, 53, 214, 54, 8, 13, 95, 31, 61, 116, 178, 225, 22, 170, 46, 128, 185, 104, 3, 31, 138, 178, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}