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: 8a90f7333905f2899cc8f0a27d4362d5593a37ff40c2ab71911bd0135f1c4f90
Tx prefix hash: 360d694f7858f82f52b052375e4e3aa725faf64636cb606311911a8c00eee38b
Tx public key: b2018e4763904a5d370ecc6254fc8456640929ce2e8fbdf7e14db739314de6ea
| Timestamp: 1780128961 | Timestamp [UTC]: 2026-05-30 08:16:01 | Age [y:d:h:m:s]: 00:009:15:02:52 |
| Block: 4928 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2958 | RingCT/type: yes/0 |
| Extra: 01b2018e4763904a5d370ecc6254fc8456640929ce2e8fbdf7e14db739314de6ea02090000000426697be300 | ||
1 output(s) for total of 34.855275169384 HMNY
| stealth address | amount | amount idx | tag |
| 00: da0322d0196a973781e9cba2f0ed61bfc2a61f0ef055bef8c915f9251bfca4c2 | 34.855275169384 | 6255 of 0 | <a0> |
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": 4988,
"vin": [ {
"gen": {
"height": 4928
}
}
],
"vout": [ {
"amount": 34855275169384,
"target": {
"tagged_key": {
"key": "da0322d0196a973781e9cba2f0ed61bfc2a61f0ef055bef8c915f9251bfca4c2",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 178, 1, 142, 71, 99, 144, 74, 93, 55, 14, 204, 98, 84, 252, 132, 86, 100, 9, 41, 206, 46, 143, 189, 247, 225, 77, 183, 57, 49, 77, 230, 234, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}