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: 4cb84027afd7f62b318f717083cead413226f6fc0659340f17b223e34e33522c
Tx prefix hash: 9b154c0658e5b2f882e12c7854cc1ebe6f82ce4c6247366c1606b83a6bdfd557
Tx public key: ad1cc01913a58dc6d787d7035e751aae2aae622b45a088e5b33549ec15215b9d
| Timestamp: 1779870801 | Timestamp [UTC]: 2026-05-27 08:33:21 | Age [y:d:h:m:s]: 00:012:14:45:32 |
| Block: 2801 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5085 | RingCT/type: yes/0 |
| Extra: 01ad1cc01913a58dc6d787d7035e751aae2aae622b45a088e5b33549ec15215b9d02090000000226697be300 | ||
1 output(s) for total of 34.996967959461 HMNY
| stealth address | amount | amount idx | tag |
| 00: c49c531857c5ff3f09498d4f4a18cb19ccd2ad019c10cacaf579a88e81f1aea2 | 34.996967959461 | 3315 of 0 | <aa> |
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": 2861,
"vin": [ {
"gen": {
"height": 2801
}
}
],
"vout": [ {
"amount": 34996967959461,
"target": {
"tagged_key": {
"key": "c49c531857c5ff3f09498d4f4a18cb19ccd2ad019c10cacaf579a88e81f1aea2",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 173, 28, 192, 25, 19, 165, 141, 198, 215, 135, 215, 3, 94, 117, 26, 174, 42, 174, 98, 43, 69, 160, 136, 229, 179, 53, 73, 236, 21, 33, 91, 157, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}