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: 0a872d967ce9f2b8b4a3aaf478a0ed42cfd748e701d3d874312acf2d2db998b8
Tx prefix hash: 8d1ef41e5b9c76ca21dbee1565d0cf8dac778344cffe3e20ccd5a063d183ffee
Tx public key: a5484614d5e11775c1beffa886a60a622bd0db79b0f77268fb0defe0c99087c0
| Timestamp: 1780683845 | Timestamp [UTC]: 2026-06-05 18:24:05 | Age [y:d:h:m:s]: 00:003:07:11:52 |
| Block: 5335 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2551 | RingCT/type: yes/0 |
| Extra: 01a5484614d5e11775c1beffa886a60a622bd0db79b0f77268fb0defe0c99087c0020900000001e49593ff00 | ||
1 output(s) for total of 34.828227810551 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1cb64398e22b52c5bf1d7d660e773cf64259c63a0eaf09c639dbfc414dba946e | 34.828227810551 | 6766 of 0 | <97> |
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": 5395,
"vin": [ {
"gen": {
"height": 5335
}
}
],
"vout": [ {
"amount": 34828227810551,
"target": {
"tagged_key": {
"key": "1cb64398e22b52c5bf1d7d660e773cf64259c63a0eaf09c639dbfc414dba946e",
"view_tag": "97"
}
}
}
],
"extra": [ 1, 165, 72, 70, 20, 213, 225, 23, 117, 193, 190, 255, 168, 134, 166, 10, 98, 43, 208, 219, 121, 176, 247, 114, 104, 251, 13, 239, 224, 201, 144, 135, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}