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: c5bb61bcf7ab7386b0ef12272e26cc382c91d8f4cdfaca9d1e45382cb597fc8e
Tx prefix hash: bd4db5f0fe0e484e1e2a2ddb1b1832fdf910250844feb679da52b8d7e6789ae6
Tx public key: 64463ffe4564b245152d456171a961d37731dff41cad52d46f05a54c8701b802
| Timestamp: 1780688543 | Timestamp [UTC]: 2026-06-05 19:42:23 | Age [y:d:h:m:s]: 00:003:05:53:34 |
| Block: 5533 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2353 | RingCT/type: yes/0 |
| Extra: 0164463ffe4564b245152d456171a961d37731dff41cad52d46f05a54c8701b802020900000001e49593ff00 | ||
1 output(s) for total of 34.815077225964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 388c9c223534f4fb5ee53c428aedf1256e4f61c68298db7406c228e2aff3dfe4 | 34.815077225964 | 6976 of 0 | <4d> |
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": 5593,
"vin": [ {
"gen": {
"height": 5533
}
}
],
"vout": [ {
"amount": 34815077225964,
"target": {
"tagged_key": {
"key": "388c9c223534f4fb5ee53c428aedf1256e4f61c68298db7406c228e2aff3dfe4",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 100, 70, 63, 254, 69, 100, 178, 69, 21, 45, 69, 97, 113, 169, 97, 211, 119, 49, 223, 244, 28, 173, 82, 212, 111, 5, 165, 76, 135, 1, 184, 2, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}