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: ffd944ac5bb904e9dd04c7c91fe7ec220cc1973443f19656b76b6f6c1c519f67
Tx prefix hash: d0032fda5c5a7debde171afb11ad290dc410899982cfa9eb69311c531d22b07e
Tx public key: 1d2c5fd4b7d86f092966fb96921507d35a9674ea97a9dfce66539db50336e9b3
| Timestamp: 1779986901 | Timestamp [UTC]: 2026-05-28 16:48:21 | Age [y:d:h:m:s]: 00:011:10:50:29 |
| Block: 3963 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3984 | RingCT/type: yes/0 |
| Extra: 011d2c5fd4b7d86f092966fb96921507d35a9674ea97a9dfce66539db50336e9b302090000000226697be300 | ||
1 output(s) for total of 34.922815028656 HMNY
| stealth address | amount | amount idx | tag |
| 00: 51d0f65862be664aef2f520152a8169d900a589bb15657eee4f996680589c9ea | 34.922815028656 | 4885 of 0 | <15> |
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": 4023,
"vin": [ {
"gen": {
"height": 3963
}
}
],
"vout": [ {
"amount": 34922815028656,
"target": {
"tagged_key": {
"key": "51d0f65862be664aef2f520152a8169d900a589bb15657eee4f996680589c9ea",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 29, 44, 95, 212, 183, 216, 111, 9, 41, 102, 251, 150, 146, 21, 7, 211, 90, 150, 116, 234, 151, 169, 223, 206, 102, 83, 157, 181, 3, 54, 233, 179, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}