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: 4f1d43234fad95c3025c003fb27e11ed2273baac5eba29b3452156a438c7e1a9
Tx prefix hash: 2db7b248e8f9e248112ed39d74de5416bea29bf04922650d266c0c911d727465
Tx public key: ccb4c678e77a24e01839355754a5e63a469f1a5445e1e3bd04b3e89938e73ab1
| Timestamp: 1779985427 | Timestamp [UTC]: 2026-05-28 16:23:47 | Age [y:d:h:m:s]: 00:011:06:55:06 |
| Block: 3955 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3931 | RingCT/type: yes/0 |
| Extra: 01ccb4c678e77a24e01839355754a5e63a469f1a5445e1e3bd04b3e89938e73ab102090000000226697be300 | ||
1 output(s) for total of 34.920021462341 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8be71738b8d2503afb8d18408fbd9c70bc67a2414a2741512a653eb242f3d871 | 34.920021462341 | 4870 of 0 | <91> |
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": 4015,
"vin": [ {
"gen": {
"height": 3955
}
}
],
"vout": [ {
"amount": 34920021462341,
"target": {
"tagged_key": {
"key": "8be71738b8d2503afb8d18408fbd9c70bc67a2414a2741512a653eb242f3d871",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 204, 180, 198, 120, 231, 122, 36, 224, 24, 57, 53, 87, 84, 165, 230, 58, 70, 159, 26, 84, 69, 225, 227, 189, 4, 179, 232, 153, 56, 231, 58, 177, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}