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: 6bd4fe879eb46be495e94464f65b027944f61cce87778c62b5d32ec16324b084
Tx prefix hash: f1c1949cebff74c28a2430befcb2c8ff1de9dfee2e08356a0e3b1adae1eed167
Tx public key: 61e9a3669c6bf020b11feace218ad53cf891b8095fd7eff61d5d04e3303d1f0e
| Timestamp: 1780854369 | Timestamp [UTC]: 2026-06-07 17:46:09 | Age [y:d:h:m:s]: 00:001:07:49:48 |
| Block: 7557 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 329 | RingCT/type: yes/0 |
| Extra: 0161e9a3669c6bf020b11feace218ad53cf891b8095fd7eff61d5d04e3303d1f0e020900000003e49593ff00 | ||
1 output(s) for total of 34.683556706124 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ef84cca969e6a299e252cb788f9b9bd09c1be2af6d8661f83f03768b05f14bb | 34.683556706124 | 9329 of 0 | <b4> |
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": 7617,
"vin": [ {
"gen": {
"height": 7557
}
}
],
"vout": [ {
"amount": 34683556706124,
"target": {
"tagged_key": {
"key": "7ef84cca969e6a299e252cb788f9b9bd09c1be2af6d8661f83f03768b05f14bb",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 97, 233, 163, 102, 156, 107, 240, 32, 177, 31, 234, 206, 33, 138, 213, 60, 248, 145, 184, 9, 95, 215, 239, 246, 29, 93, 4, 227, 48, 61, 31, 14, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}