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: d27d8552262f398ae7da9740f2cf3431b7b821d3227f57c1b629530fc4aff98f
Tx prefix hash: 3abaaa3a3ec0e0ee7e85a5536ad504c3eb2a4fd578f6022d0363d8447eece5fb
Tx public key: 7cfd5e21397b3355a1ea1b5069ce56a8c3bd41d2a08a6ccbb4663cc07028e750
| Timestamp: 1779780471 | Timestamp [UTC]: 2026-05-26 07:27:51 | Age [y:d:h:m:s]: 00:013:18:08:06 |
| Block: 2099 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5787 | RingCT/type: yes/0 |
| Extra: 017cfd5e21397b3355a1ea1b5069ce56a8c3bd41d2a08a6ccbb4663cc07028e75002090000000226697be300 | ||
1 output(s) for total of 35.043858885813 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb8e715ff6d9ec03a03f54ce8839d40d1f38cb159b9f03587a1ae7ae650a2394 | 35.043858885813 | 2415 of 0 | <b6> |
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": 2159,
"vin": [ {
"gen": {
"height": 2099
}
}
],
"vout": [ {
"amount": 35043858885813,
"target": {
"tagged_key": {
"key": "eb8e715ff6d9ec03a03f54ce8839d40d1f38cb159b9f03587a1ae7ae650a2394",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 124, 253, 94, 33, 57, 123, 51, 85, 161, 234, 27, 80, 105, 206, 86, 168, 195, 189, 65, 210, 160, 138, 108, 203, 180, 102, 60, 192, 112, 40, 231, 80, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}