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: 3c10b20ec2cbb0141d3b2c3bcebce9ec451fca0edd929d9c832d9fb743ac3f53
Tx prefix hash: 7818cc5242c796dca261e59c9df2b08548ddbca3b8e8092e82806cd75dc7d984
Tx public key: 37d212273f2d6fec8b78aed1d4f607fd74d26c976e323a3b8ce41f9cf55b4a12
| Timestamp: 1780804068 | Timestamp [UTC]: 2026-06-07 03:47:48 | Age [y:d:h:m:s]: 00:010:04:48:26 |
| Block: 6902 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1843 | RingCT/type: yes/0 |
| Extra: 0137d212273f2d6fec8b78aed1d4f607fd74d26c976e323a3b8ce41f9cf55b4a12020900000001e49593ff00 | ||
1 output(s) for total of 34.724287976866 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6e6b160557e50a3ca352f4f28760e8774115e5107706f7cd3d75944f052105a5 | 34.724287976866 | 8516 of 0 | <aa> |
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": 6962,
"vin": [ {
"gen": {
"height": 6902
}
}
],
"vout": [ {
"amount": 34724287976866,
"target": {
"tagged_key": {
"key": "6e6b160557e50a3ca352f4f28760e8774115e5107706f7cd3d75944f052105a5",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 55, 210, 18, 39, 63, 45, 111, 236, 139, 120, 174, 209, 212, 246, 7, 253, 116, 210, 108, 151, 110, 50, 58, 59, 140, 228, 31, 156, 245, 91, 74, 18, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}