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: 3cd37ff14226ecd0caa4a80e48453137712cb5a345423d530c7820f04b5f76ee
Tx prefix hash: fc64986ed4725c47821821b0d41d5f775f2849548e029be6741502f5a341ff00
Tx public key: 6feae964042bb1e1fd3cc601feab70a9fdb2ab3770850d724a76e4b6df5e735d
| Timestamp: 1779453937 | Timestamp [UTC]: 2026-05-22 12:45:37 | Age [y:d:h:m:s]: 00:017:14:53:13 |
| Block: 360 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7587 | RingCT/type: yes/0 |
| Extra: 016feae964042bb1e1fd3cc601feab70a9fdb2ab3770850d724a76e4b6df5e735d02090000000393369e7d00 | ||
1 output(s) for total of 35.160288230311 HMNY
| stealth address | amount | amount idx | tag |
| 00: b30f3337ab459d27d6b98ff004bd6485c3cf1aac3d0a9c7cb444a023b441b2f0 | 35.160288230311 | 356 of 0 | <3e> |
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": 420,
"vin": [ {
"gen": {
"height": 360
}
}
],
"vout": [ {
"amount": 35160288230311,
"target": {
"tagged_key": {
"key": "b30f3337ab459d27d6b98ff004bd6485c3cf1aac3d0a9c7cb444a023b441b2f0",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 111, 234, 233, 100, 4, 43, 177, 225, 253, 60, 198, 1, 254, 171, 112, 169, 253, 178, 171, 55, 112, 133, 13, 114, 74, 118, 228, 182, 223, 94, 115, 93, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}