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: 7404b6e5d3cca0260e43cd2638e80f8100d7dd1f3436dc422b9d0d529bf2d392
Tx prefix hash: 75dd218f451adca1c9b7c73f397cd5974a1747a0a5c983f8c69fed3d1470f0cf
Tx public key: f7a7f222294e59f7d5403aef1525d791148906599549e60ff6f52d35431fea8b
| Timestamp: 1780690847 | Timestamp [UTC]: 2026-06-05 20:20:47 | Age [y:d:h:m:s]: 00:003:04:26:00 |
| Block: 5687 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2199 | RingCT/type: yes/0 |
| Extra: 01f7a7f222294e59f7d5403aef1525d791148906599549e60ff6f52d35431fea8b020900000001e49593ff00 | ||
1 output(s) for total of 34.804852426508 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a6fb8598d6d1b095c23ac80833394b7b3a23271d703b3749b4e303ee10e803d | 34.804852426508 | 7138 of 0 | <fc> |
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": 5747,
"vin": [ {
"gen": {
"height": 5687
}
}
],
"vout": [ {
"amount": 34804852426508,
"target": {
"tagged_key": {
"key": "8a6fb8598d6d1b095c23ac80833394b7b3a23271d703b3749b4e303ee10e803d",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 247, 167, 242, 34, 41, 78, 89, 247, 213, 64, 58, 239, 21, 37, 215, 145, 20, 137, 6, 89, 149, 73, 230, 15, 246, 245, 45, 53, 67, 31, 234, 139, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}