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: 69af2218558de8b780df3df2f5f9cff214a4df999c0a50a411f9cb8904ef6391
Tx prefix hash: 02651275b1ec1c087898c31744edc1efffd15fde3698012380acc9e886ed7a2b
Tx public key: d16095dd0e0dacb185e18ad9dd978a75551743cdd8bd188c19d7cf2554330a54
| Timestamp: 1779799133 | Timestamp [UTC]: 2026-05-26 12:38:53 | Age [y:d:h:m:s]: 00:013:10:40:00 |
| Block: 2289 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5597 | RingCT/type: yes/0 |
| Extra: 01d16095dd0e0dacb185e18ad9dd978a75551743cdd8bd188c19d7cf2554330a5402090000000126697be300 | ||
1 output(s) for total of 35.036166611898 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f719f3cd0e7fd4b4392e08fedea85f1f59a61a7f355a4efcbe90279713e8ffc | 35.036166611898 | 2667 of 0 | <15> |
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": 2349,
"vin": [ {
"gen": {
"height": 2289
}
}
],
"vout": [ {
"amount": 35036166611898,
"target": {
"tagged_key": {
"key": "4f719f3cd0e7fd4b4392e08fedea85f1f59a61a7f355a4efcbe90279713e8ffc",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 209, 96, 149, 221, 14, 13, 172, 177, 133, 225, 138, 217, 221, 151, 138, 117, 85, 23, 67, 205, 216, 189, 24, 140, 25, 215, 207, 37, 84, 51, 10, 84, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}