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: d471e836c6d6f85f832ebabad4bc0e0429209cc6b37dcdfe86d61aee411d8331
Tx prefix hash: 8eeda3bad7d2eadc1d232b9ccb6fbed7af15c53622cf7a64ad4bdff25110a4a1
Tx public key: 1629b0a506acf8ae13477a3bb1e19ef5259ceb79f35197d0aa700a3733ea754e
| Timestamp: 1780690161 | Timestamp [UTC]: 2026-06-05 20:09:21 | Age [y:d:h:m:s]: 00:011:13:05:45 |
| Block: 5640 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3105 | RingCT/type: yes/0 |
| Extra: 011629b0a506acf8ae13477a3bb1e19ef5259ceb79f35197d0aa700a3733ea754e020900000001e49593ff00 | ||
1 output(s) for total of 34.807972663760 HMNY
| stealth address | amount | amount idx | tag |
| 00: 231d6611f82e79df1a7f8bfa09384f2973e420bb6f5c0b667e7756c193aa1e6a | 34.807972663760 | 7087 of 0 | <4f> |
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": 5700,
"vin": [ {
"gen": {
"height": 5640
}
}
],
"vout": [ {
"amount": 34807972663760,
"target": {
"tagged_key": {
"key": "231d6611f82e79df1a7f8bfa09384f2973e420bb6f5c0b667e7756c193aa1e6a",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 22, 41, 176, 165, 6, 172, 248, 174, 19, 71, 122, 59, 177, 225, 158, 245, 37, 156, 235, 121, 243, 81, 151, 208, 170, 112, 10, 55, 51, 234, 117, 78, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}