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: 9508f9cecaea1a68480279678343d8305f470c0e8f44b334373d27e298b03f73
Tx prefix hash: 7900587812540e675da4dec82745d5d943e521d6357604a600b11822a2dcbb53
Tx public key: ea8fe5a1c721ee7e4f2a27b1b78f2f219bd5820fe35a30b22ee79e4a8a40c001
| Timestamp: 1780693112 | Timestamp [UTC]: 2026-06-05 20:58:32 | Age [y:d:h:m:s]: 00:003:06:52:26 |
| Block: 5848 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2119 | RingCT/type: yes/0 |
| Extra: 01ea8fe5a1c721ee7e4f2a27b1b78f2f219bd5820fe35a30b22ee79e4a8a40c001020900000001e49593ff00 | ||
1 output(s) for total of 34.794166074182 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8642331485bce508f4bce690b7dab9368bccb7dc5c5385a98fb90b8cd73df3d7 | 34.794166074182 | 7305 of 0 | <93> |
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": 5908,
"vin": [ {
"gen": {
"height": 5848
}
}
],
"vout": [ {
"amount": 34794166074182,
"target": {
"tagged_key": {
"key": "8642331485bce508f4bce690b7dab9368bccb7dc5c5385a98fb90b8cd73df3d7",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 234, 143, 229, 161, 199, 33, 238, 126, 79, 42, 39, 177, 183, 143, 47, 33, 155, 213, 130, 15, 227, 90, 48, 178, 46, 231, 158, 74, 138, 64, 192, 1, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}