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: 00feadb0c3860f8c517d35f182dcb4ec71d5e806e226560ddb22e1ae6d1aa6f6
Tx prefix hash: a87fd1af6efb08298f9613e4aeb58dd6b4e4766a40b0c30013efa594769d2c33
Tx public key: 6309da20b7af9a6e29829bf0dc7c19225cd5c65582bb69d2f370ca708716c8fe
| Timestamp: 1779876373 | Timestamp [UTC]: 2026-05-27 10:06:13 | Age [y:d:h:m:s]: 00:012:15:29:44 |
| Block: 2891 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4995 | RingCT/type: yes/0 |
| Extra: 016309da20b7af9a6e29829bf0dc7c19225cd5c65582bb69d2f370ca708716c8fe02090000000226697be300 | ||
1 output(s) for total of 34.990960841633 HMNY
| stealth address | amount | amount idx | tag |
| 00: 91922f65e2210d01e5050d6961cb1e7de9cf111e1f49c407509c53eddea12276 | 34.990960841633 | 3423 of 0 | <7a> |
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": 2951,
"vin": [ {
"gen": {
"height": 2891
}
}
],
"vout": [ {
"amount": 34990960841633,
"target": {
"tagged_key": {
"key": "91922f65e2210d01e5050d6961cb1e7de9cf111e1f49c407509c53eddea12276",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 99, 9, 218, 32, 183, 175, 154, 110, 41, 130, 155, 240, 220, 124, 25, 34, 92, 213, 198, 85, 130, 187, 105, 210, 243, 112, 202, 112, 135, 22, 200, 254, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}