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: 146d15bea84e5bb4bf7010b230f71c85c9b1651dce1a32a64a84d346a4cdf2a8
Tx prefix hash: bb774a8ef45663e311a42d3c88b1c19b1e616c41a1ad700dd064a109c6a28b40
Tx public key: ba6745c5a0b0ac7e668c042f9e474a044c4e32a6f068c3536a76c0066c43b48a
| Timestamp: 1779772071 | Timestamp [UTC]: 2026-05-26 05:07:51 | Age [y:d:h:m:s]: 00:013:20:28:06 |
| Block: 2024 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5862 | RingCT/type: yes/0 |
| Extra: 01ba6745c5a0b0ac7e668c042f9e474a044c4e32a6f068c3536a76c0066c43b48a02090000000326697be300 | ||
1 output(s) for total of 35.048872313399 HMNY
| stealth address | amount | amount idx | tag |
| 00: f21c0e3dbb449fd78c062e9a5a7373cd6c1a232ce8218cd3e9fff70b1c1094b2 | 35.048872313399 | 2312 of 0 | <bc> |
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": 2084,
"vin": [ {
"gen": {
"height": 2024
}
}
],
"vout": [ {
"amount": 35048872313399,
"target": {
"tagged_key": {
"key": "f21c0e3dbb449fd78c062e9a5a7373cd6c1a232ce8218cd3e9fff70b1c1094b2",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 186, 103, 69, 197, 160, 176, 172, 126, 102, 140, 4, 47, 158, 71, 74, 4, 76, 78, 50, 166, 240, 104, 195, 83, 106, 118, 192, 6, 108, 67, 180, 138, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}