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: c70000a183f69553e9b65830f6ecacda66060561281480f315b53582ecc79b48
Tx prefix hash: c97f66d7dc143d7de9b02aff452aa21eee1dee921923e69d1e4c2c740b0c56e3
Tx public key: 4085570028ec8eb9bff05c8d4120e8f1d4a4a507739b2a558f1c4b7e455c4130
| Timestamp: 1780993118 | Timestamp [UTC]: 2026-06-09 08:18:38 | Age [y:d:h:m:s]: 00:000:09:01:25 |
| Block: 8270 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 473 | RingCT/type: yes/0 |
| Extra: 014085570028ec8eb9bff05c8d4120e8f1d4a4a507739b2a558f1c4b7e455c4130020900000001e49593ff00 | ||
1 output(s) for total of 34.633801542771 HMNY
| stealth address | amount | amount idx | tag |
| 00: b610e7ea1732f41b70cfea4137682a3f87cbb771476e7463ce8b8a655cb6e29d | 34.633801542771 | 10234 of 0 | <5a> |
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": 8330,
"vin": [ {
"gen": {
"height": 8270
}
}
],
"vout": [ {
"amount": 34633801542771,
"target": {
"tagged_key": {
"key": "b610e7ea1732f41b70cfea4137682a3f87cbb771476e7463ce8b8a655cb6e29d",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 64, 133, 87, 0, 40, 236, 142, 185, 191, 240, 92, 141, 65, 32, 232, 241, 212, 164, 165, 7, 115, 155, 42, 85, 143, 28, 75, 126, 69, 92, 65, 48, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}