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: 661c71f327c027e44f51d589c67321163568558dd7608bb98a6f15c6523f329a
Tx prefix hash: c0cf80cc86cf239d7bd31b1c0584428c5e4f0d3ccb63b8a1c3041bd32fe921b0
Tx public key: 24c29e71672dd7c33ada9e8cf9396de37307ea01b5b19d4d8469a9dd8a8ae854
| Timestamp: 1779966542 | Timestamp [UTC]: 2026-05-28 11:09:02 | Age [y:d:h:m:s]: 00:011:12:09:51 |
| Block: 3812 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4074 | RingCT/type: yes/0 |
| Extra: 0124c29e71672dd7c33ada9e8cf9396de37307ea01b5b19d4d8469a9dd8a8ae85402090000000326697be300 | ||
1 output(s) for total of 34.929547236140 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1da72a5efbe039dad424cbbe46eefb49d9fb876a2bb662ecd7c62df0dedc87c | 34.929547236140 | 4641 of 0 | <2a> |
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": 3872,
"vin": [ {
"gen": {
"height": 3812
}
}
],
"vout": [ {
"amount": 34929547236140,
"target": {
"tagged_key": {
"key": "a1da72a5efbe039dad424cbbe46eefb49d9fb876a2bb662ecd7c62df0dedc87c",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 36, 194, 158, 113, 103, 45, 215, 195, 58, 218, 158, 140, 249, 57, 109, 227, 115, 7, 234, 1, 181, 177, 157, 77, 132, 105, 169, 221, 138, 138, 232, 84, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}