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: 03657b6bed679f09bcb6200fd29de6dbaff6865f92625bf2859b6e8714eadcca
Tx prefix hash: f39c9336691580f8783f56a3fdda4577d3e97d2d59f7fca30473600b8082811c
Tx public key: b41aa96812a155d2a204ea48c65db5f270d7ae5ef4813b0748d71937a043c2ef
| Timestamp: 1780844825 | Timestamp [UTC]: 2026-06-07 15:07:05 | Age [y:d:h:m:s]: 00:001:07:17:44 |
| Block: 7498 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 388 | RingCT/type: yes/0 |
| Extra: 01b41aa96812a155d2a204ea48c65db5f270d7ae5ef4813b0748d71937a043c2ef020900000002e49593ff00 | ||
1 output(s) for total of 34.684836498686 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c73a30faab1216a916953936da3db42c8d7a2dee3238d2df4daa768e1f9cff8 | 34.684836498686 | 9240 of 0 | <4a> |
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": 7558,
"vin": [ {
"gen": {
"height": 7498
}
}
],
"vout": [ {
"amount": 34684836498686,
"target": {
"tagged_key": {
"key": "5c73a30faab1216a916953936da3db42c8d7a2dee3238d2df4daa768e1f9cff8",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 180, 26, 169, 104, 18, 161, 85, 210, 162, 4, 234, 72, 198, 93, 181, 242, 112, 215, 174, 94, 244, 129, 59, 7, 72, 215, 25, 55, 160, 67, 194, 239, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}